How do I install the Proposal skill?

Run npx skillmds add vukhanhtruong/proposal in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Proposal safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Proposal?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Proposal free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Proposal?

vukhanhtruong (@vukhanhtruong) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Proposal by vukhanhtruong — Agent Skill

Name: Proposal
Rating: 4.2 (5 reviews)
Author: vukhanhtruong

Proposal

Assemble a pre-sales client proposal from analyze-requirements and estimate outputs — interviewed client context, one offered scenario as a price range, and a print-ready client page. Use when the user asks for a proposal, a client pitch document, a quote document, or "something I can send the client".

vukhanhtruong 0d64612 25 files · 52.0 KB Updated Sep 10, 2026

File contents

proposal

Assemble a pre-sales client proposal: proposal.md as the source of truth and a self-contained, print-ready proposal.html the user can send or print to PDF.

Hard rules

Assembly only — never re-analyze. Architecture facts come from ARCHITECTURE.md; every number comes from estimation.json via scripts/derive.mjs. A number the derivation didn't produce does not go in the document.
Both prerequisites are hard: no ARCHITECTURE.md or no estimation.json → stop and name the skill to run (analyze-requirements / estimate).
One scenario reaches the client — the one picked in the interview, presented as a range. The others never leak.
node scripts/validate.mjs must exit 0 before the page renders; render.mjs re-runs the same checks and refuses on findings.
Human review of proposal.md before anything is rendered for or sent to a client.

Flow

Prereq gate: ARCHITECTURE.md and estimation.json both exist, or stop.
Interview: follow references/interview.md — client context, tech level, scenario pick, validity, firm profile (with storage-scope choice).
Figures: node scripts/derive.mjs --estimation <dir>/estimation.json --scenario <id> --out <dir>/proposal-figures.json — the only numbers allowed in the document.
Write: proposal.md per references/writing.md (ten sections, frontmatter contract, tech-level language).
Validate: node scripts/validate.mjs --md <dir>/proposal.md --estimation <dir>/estimation.json — fix findings, re-run until clean.
Fresh-eyes review: dispatch a subagent per references/review.md; fix findings, re-run validate; one re-review cycle max.
Human review: show the user proposal.md and wait for approval.
Render: node scripts/render.mjs --md <dir>/proposal.md --estimation <dir>/estimation.json --mermaid-bundle <path> --out <dir>/dist — reuse the mermaid bundle built for the analyze-requirements viewer (analyze-requirements references/viewer.md §1). <dir>/dist/ is the one rendered-pages folder: proposal.html ships beside index.html and estimate.html; proposal.html itself carries no link back.
Serve: node ../analyze-requirements/scripts/serve.mjs <dir>; report the URL.

Placement

proposal.md lives beside ARCHITECTURE.md and estimation.md. proposal.html follows the estimate.html rule: into the rendered viewer's directory when one exists, else beside proposal.md.

Dependency

Node ≥ 20. Scripts are dependency-free.

---name: proposaldescription: Assemble a pre-sales client proposal from analyze-requirements and estimate outputs — interviewed client context, one offered scenario as a price range, and a print-ready client page. Use when the user asks for a proposal, a client pitch document, a quote document, or "something I can send the client".---# proposalAssemble a pre-sales client proposal: proposal.md as the source of truth anda self-contained, print-ready proposal.html the user can send or print toPDF.## Hard rules1. Assembly only — never re-analyze. Architecture facts come from ARCHITECTURE.md; every number comes from estimation.json via `scripts/derive.mjs`. A number the derivation didn't produce does not go in the document.2. Both prerequisites are hard: no ARCHITECTURE.md or no estimation.json → stop and name the skill to run (`analyze-requirements` / `estimate`).3. One scenario reaches the client — the one picked in the interview, presented as a range. The others never leak.4. `node scripts/validate.mjs` must exit 0 before the page renders; `render.mjs` re-runs the same checks and refuses on findings.5. Human review of proposal.md before anything is rendered for or sent to a client.## Flow1. **Prereq gate**: ARCHITECTURE.md and estimation.json both exist, or stop.2. **Interview**: follow `references/interview.md` — client context, tech level, scenario pick, validity, firm profile (with storage-scope choice).3. **Figures**: `node scripts/derive.mjs --estimation <dir>/estimation.json --scenario <id> --out <dir>/proposal-figures.json` — the only numbers allowed in the document.4. **Write**: proposal.md per `references/writing.md` (ten sections, frontmatter contract, tech-level language).5. **Validate**: `node scripts/validate.mjs --md <dir>/proposal.md --estimation <dir>/estimation.json` — fix findings, re-run until clean.6. **Fresh-eyes review**: dispatch a subagent per `references/review.md`; fix findings, re-run validate; one re-review cycle max.7. **Human review**: show the user proposal.md and wait for approval.8. **Render**: `node scripts/render.mjs --md <dir>/proposal.md --estimation <dir>/estimation.json --mermaid-bundle <path> --out <dir>/dist` — reuse the mermaid bundle built for the analyze-requirements viewer (analyze-requirements `references/viewer.md` §1). `<dir>/dist/` is the one rendered-pages folder: proposal.html ships beside index.html and estimate.html; proposal.html itself carries no link back.9. **Serve**: `node ../analyze-requirements/scripts/serve.mjs <dir>`; report the URL.## Placementproposal.md lives beside ARCHITECTURE.md and estimation.md. proposal.htmlfollows the estimate.html rule: into the rendered viewer's directory whenone exists, else beside proposal.md.## DependencyNode ≥ 20. Scripts are dependency-free.

Frequently asked questions