proposal-writer · genspark-ai — Claude Code skill: what it does, how to install
proposal-writer turns a requirement or a rough idea into a Word proposal with goals, a recommended option, milestones, budget and risks.
Apache-2.0 ★ 12,746 updated 2026-10-29
npx skills add genspark-ai/genoffice --skill proposal-writer -a claude-codeWhat proposal-writer does
Give the skill a requirement, a spoken description or half-formed idea and it returns a proposal you can hand to a reviewer. First it pins down the audience and the approver, because an internal approval memo, a client solution and a renovation plan differ in length and tone. Goals, budget and time limits, alternatives and the acceptance method all get collected in one pass.
The structure stays fixed. One recommended option plus at least one alternative, judged on the same dimensions. Milestones sit in four columns: phase, deliverable, date, owner. Every budget line that is an estimate carries “est.” and the basis for it. A risk table covers schedule, cost, dependencies and compliance. Sections open with the conclusion, support follows. The file is named <Project Name> Proposal vN.
Client versions carry the quote and delivery commitments only, so internal costs and margin have no place there; a cost breakdown belongs to an internal proposal. Where the requirement has no figures, the document keeps “TBD” rather than inventing a number. Review copies run 5 to 10 pages, client copies 3 to 6.
What it helps with
- draft a project proposal from a bare requirement
- weigh the recommended option against an alternative on cost and risk
- itemise a budget with estimates marked and their basis given
- cover schedule, cost, dependency and compliance risks
- produce a client copy without internal costs
Example prompts for the agent
- Write a project proposal from these requirements and save it as a Word document
- Turn this idea into a solution proposal for the client, leave internal costs out
- Diff this against the earlier proposal first, then rewrite it and list the changes under decisions required
How to install proposal-writer
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill proposal-writer -a claude-code2Manually: put the files in place
~/.claude/skills/proposal-writer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/proposal-writer/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill proposal-writer -a codex2Manually: put the files in place
.agents/skills/proposal-writer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill proposal-writer -a cursor2Manually: put the files in place
.cursor/skills/proposal-writer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install genspark-ai/genoffice skills/recommended/proposal-writer2Manually: put the files in place
.github/skills/proposal-writer/SKILL.md1Skills CLI (Vercel)
npx skills add genspark-ai/genoffice --skill proposal-writer -a gemini-cli2Platform CLI
gemini skills install https://github.com/genspark-ai/genoffice --path skills/recommended/proposal-writerManually: put the files in place
.devin/skills/proposal-writer/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about proposal-writer
How do I install proposal-writer in Claude Code?
Run npx skills add genspark-ai/genoffice --skill proposal-writer -a claude-code. The skill file lands at ~/.claude/skills/proposal-writer/SKILL.md.
What does proposal-writer do?
It builds a Word proposal from a requirement or an idea: verifiable goals, a recommended option with an alternative, milestones, an itemised budget and a risk table. When it finishes it points out the two or three spots where your data or a decision is still needed.
How is a client proposal different from an internal one?
The client copy holds the quote and delivery commitments only. Cost breakdowns stay in internal proposals.
Source text
SKILL.md · Apache-2.0
--- name: proposal-writer description: Turn a requirement or idea into a reviewable project or solution proposal covering goals, design, milestones, budget and risks, delivered as a Word document category: office scenarios: Project proposals | Solution proposals | Approval presentations quickPrompts: Write a project proposal from these requirements | Expand this idea into a solution document ready for review metadata: version: 1.0.0 --- 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. - One-page summary: problem, goals, recommended option, total investment, key risks, one line each, so that someone who reads only the first page can decide. - Background and current state, goals and success criteria (each goal with an acceptance metric). - Solution design: detailed recommended option plus an alternatives comparison table (dimensions x options). - Implementation plan: milestone table. Resources and budget: itemised table, with the total row stating the formula and whether tax is included. - Risks and mitigations: table with columns risk / likelihood / impact / mitigation / owner. - Decisions required: the questions the approver must settle on the spot. ## Style - Each section leads with a conclusion sentence, then the support; numbers carry units and definitions; no piling up of adjectives. - Client-facing proposals do not show internal costs or margins, only the quote and delivery commitments; cost breakdowns belong in internal proposals only. ## Rules - Goals must be verifiable: write "support tickets down 20% three months after launch", not "improve user experience". - The risks section covers at least four categories: schedule, cost, dependencies, compliance; never "no significant risks". - Content touching licences, approvals or data compliance uses the placeholder "subject to local rules / company policy" without drawing conclusions. - When the user has an earlier version, compare the differences first, then rewrite, keeping the original numbering and terminology and listing the changes under decisions required. - The alternative is not a foil; state clearly under what conditions it would be the better choice. ## Output One Word document: 5 to 10 pages for review, 3 to 6 pages for clients. The reply holds only the open items, not a restatement of the body.
© genspark-ai · Apache-2.0 · genspark-ai/genoffice
Similar skills
All skills for Office documents →proposal-writer by other authors comes first.