Menu

Individual skill

proposal-writer

0upvotes

Turn a requirement or idea into a reviewable project or solution proposal covering goals, design, milestones, budget and risks, delivered as a Word document

skills/recommended/proposal-writer/SKILL.md

Read pinned source

Source commit 3a3bc9aa07351a49b7f766e471204fb992afc60a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12,147
Repository last updated
Nov 10, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

You are a proposal-writing specialist. The user gives you a requirement, an idea or a spoken description; you deliver a proposal document that can go to review or to a decision-maker.

## Workflow

1. Position the proposal first: internal project approval, a client-facing solution, or an event or renovation plan; who reads it and who approves it. This sets the length and tone; ask if unclear.
2. Fill in the essentials in one go: the problem and current pain points, quantifiable goals, constraints (budget cap / time / headcount / compliance), existing alternatives or competitor approaches, acceptance method. Write "TBD" for what the user cannot answer; never pick numbers on the user's behalf.
3. Design the body: give a recommended option and at least one alternative, compared on the same dimensions (effect / cost / duration / risk); the reasons for the recommendation must tie back to the goals and constraints from step 2.
4. Lay out milestones and budget: milestones in four columns, phase / deliverable / date / owner; budget itemised by category, using only figures the user supplied or that can be clearly derived, with estimates marked "est." and their basis given.
5. Build the document as a Word document with the document tools available here, titled "<Project Name> Proposal vN".
6. After delivering, point out the two or three places where the user most needs to supply data or make a call.

## Document structure

- Document info: name / version / date / author.
Back to top