statement-of-work
Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes. Use when asked to write a SOW, a scope of work, a project agreement, or to formalise what was agreed after a proposal. Produces an SOW — scope (and explicit exclusions), deliverables with acceptance criteria, timeline & milestones, payment schedule, assumptions, change-control, and terms. The contract layer after the proposal sells.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work --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.
# Statement of Work Skill The proposal wins the deal; the SOW protects it. Most consulting pain — scope creep, "that's not what I meant," late or withheld payment — traces to a vague SOW. This skill writes a precise one: exactly what's in (and explicitly *out*), how each deliverable is accepted, when money changes hands, and how changes are handled — so both sides are protected. ## Required Inputs Ask for these only if they aren't already provided: - **The engagement** — parties, and what was agreed (often from a [`consulting-proposal`](../consulting-proposal/SKILL.md)). - **Deliverables** — the concrete outputs and how "done" is judged. - **Timeline & dependencies** — milestones, and what you need *from the client* and by when. - **Commercials** — total fee, payment schedule/triggers, and rate for out-of-scope/change work. ## Output Format ### Statement of Work — [project] **Between:** [provider] and [client] · **Effective:** [date] **1. Scope** — what will be done, specifically. Then **explicit exclusions** ("Out of scope: …") — the most valuable section; unsaid scope is assumed-included by clients. **2. Deliverables & acceptance criteria** — each deliverable with **how it's acce
- Required Inputs
- Output Format
- Statement of Work — [project]
- Quality Checks
- Anti-Patterns
- Based On
What does the statement-of-work skill do?
Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes. Use when asked to write a SOW, a scope of work, a project agreement, or to formalise what was agreed after a proposal. Produces an SOW — scope (and explicit exclusions), deliverables with acceptance criteria, timeline & milestones, payment schedule, assumptions, change-control, and terms. The contract layer after the proposal sells.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work --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.