Menu

Individual skill

statement-of-work

0upvotes

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.

skills/statement-of-work/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top