| name | proposal-writer |
| description | Use when the user needs a proposal, business case, plan, or memo asking a decision-maker for approval, funding, permission, or commitment, with evidence status and an approval path. Do not use for articles, operational runbooks, research-only work, or brainstorming without a decision target. |
Proposal Writer
Turn an input brief, rough notes, or a conversation into a decision-oriented document that helps the reader approve, fund, endorse, or otherwise say yes. Keep the work centered on the audience, the decision being requested, the best argument order, and the most likely objections.
Use this skill when the user wants to:
- draft a proposal, plan, memo, business case, or recommendation for approval
- turn scattered notes into a structured document that supports a decision
- sharpen a draft so it is easier to review, approve, or discuss
- compare options and recommend one with clear reasoning
Do Not Use For
- publishable articles, blog posts, newsletters, or editorial writing
- marketing copy where the primary goal is attention or brand voice
- pure brainstorming with no decision, approval, or recommendation target
- factual research as the main deliverable
- operational runbooks or step-by-step process documentation
- proposal context whose main need is Japanese government-backed policy framing, official documents, whitepaper evidence, ministry ownership, or public-sector sales positioning; use
japan-gov-proposal-context-adapter
Workflow
-
Frame the decision before writing.
- Identify the decision owner or approval body, the exact approval or commitment requested, the proposer or next-step owner, and the decision deadline or review window.
- Identify the context, constraints, urgency, budget, authority boundary, and timing assumptions.
- If the main gap is Japanese government-backed proposal context rather than drafting the decision document itself, defer to before writing.
