purchase-justification
Write the purchase request that gets approved — the cost-of-not-buying framing, the ROI math at the approver's altitude, the alternatives-considered section that preempts the obvious pushback, and the right-sized ask for the approval tier. Use when asked justify this tool/hire/equipment purchase, write the budget request, my requests keep getting deferred, or make the business case for this spend. Produces the justification memo: the problem priced, the ROI shown, alternatives dispatched, and the ask sized to its approval path.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill purchase-justification --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.
# Purchase Justification Skill Purchase requests die of vagueness, not price: "we need this tool, it's $8k" gives the approver nothing to weigh, so deferral — the polite no — wins by default. The justification that works is the [proposal-skeleton](../proposal-skeleton/SKILL.md) specialized for spend: the *problem priced first* (what not-buying costs, in the approver's currency — hours, risk, revenue), the ROI math honest and conservative (one inflated payback poisons the requester's every future ask), the alternatives-considered section dispatching the obvious pushbacks ("can't we use what we have?") before they're raised, and the ask *sized to its approval tier* — because a $4,800 pilot approved this week beats a $50k platform deferred to next fiscal year. ## What This Skill Produces - **The justification memo** — one page: the priced problem, the proposal, the ROI, alternatives, the ask - **The ROI math** — conservative, assumption-labeled, with the payback period the approver can check - **The alternatives table** — do-nothing (priced), the cheaper option (honestly assessed), the requested option - **The ask sizing** — the request shaped to the approval tier and the pilot-first
- What This Skill Produces
- Required Inputs
- Framework: The Justification Rules
- Output Format
- The Problem, Priced
- The Proposal + ROI
- Alternatives Considered
- The Ask
- Quality Checks
- Anti-Patterns
What does the purchase-justification skill do?
Write the purchase request that gets approved — the cost-of-not-buying framing, the ROI math at the approver's altitude, the alternatives-considered section that preempts the obvious pushback, and the right-sized ask for the approval tier. Use when asked justify this tool/hire/equipment purchase, write the budget request, my requests keep getting deferred, or make the business case for this spend. Produces the justification memo: the problem priced, the ROI shown, alternatives dispatched, and the ask sized to its approval path.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill purchase-justification --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.