Individual skill
statement-of-work-writer
Writes a dispute-preventing statement of work with explicit inclusions and exclusions, a 2-revision-round limit, acceptance criteria, a 50-percent-upfront or milestone payment schedule, and a change-order clause, from a full template with [FILL] fields. Use when a freelancer or consultant says "write my SOW", "the client keeps adding stuff and I have nothing in writing", "how do I define scope in the contract", "what should my payment terms be", "draft a statement of work for this project", or "client won't sign off on the deliverable". Do NOT use for the persuasive proposal that wins the work - use sales-proposal-writer instead; this skill contracts work already agreed in principle.
skills/statement-of-work-writer/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 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)
- 24
- Repository last updated
- Oct 13, 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.
Read excerpt
# Statement of Work Writer
Almost every freelance dispute - unpaid invoices, endless revisions, "that was obviously included" - traces back to a scope document that only listed what IS included and stayed silent on everything else. A dispute-preventing SOW is defined as much by its exclusions as its inclusions, and it decides in advance how three predictable events get handled: the client asks for more, the client goes quiet, and the client won't say "done". This skill writes that document.
It pairs with scope-creep-defense, which enforces at delivery time what this SOW establishes at signing time. In the Freelancer / Consultant OS pack, the scope content comes from productized-service-designer. Worked example: Maya, a freelance brand designer moving from $75/hr hourly work to productized retainers, contracting her $4,900/month Brand System Retainer.
## Operating procedure
### Step 1: Collect the inputs
1. The agreed offer: deliverables, quantities, price (from productized-service-designer if productized; for Maya, the Tier 2 retainer at $4,900/month, up to 36 hours).
2. Client legal name, signer, and start date.
3. Project type: one-time project or ongoing retainer - this decides the payment schedule.
4. The 3-5 requests the client is most likely to make that are NOT included. If the freelancer cannot name them, derive them from the "outside the box" list in productized-service-designer. Label guesses as guesses and confirm with the freelancer.