proposal-skeleton
Structure an internal proposal that gets a decision — the problem-cost-options-recommendation-ask spine, the objection pre-handling that shortens the meeting, and the reversibility framing that makes yes easier. Use when asked write a proposal for the new tool or process or hire, how do I pitch this internally, structure my case for the change, or my proposals keep dying in review. Produces the proposal skeleton filled from the actual case, the objections table, the decision-sized ask, and the one-page discipline.
npx skills add mohitagw15856/pm-claude-skills --skill proposal-skeleton --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Proposal Skeleton Skill Internal proposals die of three causes: the problem arrived unpriced (so the status quo stayed free), the options section was a strawman parade (so the reader felt managed), or the ask was unsized (so "interesting" substituted for a decision). The working spine is old and undefeated: the problem *with its cost* → real options fairly stated → the recommendation with reasons → risks conceded with mitigations → a decision-sized ask with a reversibility line. One page, because proposals are read in the gap between meetings. ## What This Skill Produces - **The filled skeleton** — problem-with-cost, options, recommendation, risks, ask — from the actual case - **The objections table** — the three likely objections, pre-answered in the reader's dialect - **The ask, decision-sized** — what exactly, costing what, decided by whom, reversible how - **The one-page version** — with the appendix rule for everything that overflows ## Required Inputs Ask for these if not provided: - **The change and the evidence** — what's being proposed and what supports it (the pilot data, the incident, the quote comparisons); skeletons organize evidence, not enthusiasm - **The cost of t
- What This Skill Produces
- Required Inputs
- Framework: The Spine Rules
- Output Format
- The Problem, Priced
- Options (steelmanned)
- Recommendation
- Objections, Pre-Handled
- The Ask
- Quality Checks
- Anti-Patterns
What does the proposal-skeleton skill do?
Structure an internal proposal that gets a decision — the problem-cost-options-recommendation-ask spine, the objection pre-handling that shortens the meeting, and the reversibility framing that makes yes easier. Use when asked write a proposal for the new tool or process or hire, how do I pitch this internally, structure my case for the change, or my proposals keep dying in review. Produces the proposal skeleton filled from the actual case, the objections table, the decision-sized ask, and the one-page discipline.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill proposal-skeleton --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.