sow-generator — Claude Code skill for creating SOWs
sow-generator turns a project brief into a Statement of Work with scope, deliverables, milestones, and payment terms. Use it to prepare a consulting engagement document.
MIT 284 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill sow-generator -a claude-codeWhat sow-generator does
The skill gathers required details before drafting and researches the client with WebSearch, looking for company background, recent news, technology use, and regulatory context. It asks for missing critical terms rather than filling them in. If the scope could be read in materially different ways, it asks clarifying questions.
The SOW follows a 16-section structure, with reference materials for pricing, legal clauses, change requests, and risk management. Cross-references connect scope items to deliverables, milestones, and payment triggers. The finished file goes to sow.md in the working directory or to a path supplied by the user. For regulated industries, the workflow adds a compliance section and calls for further legal review. If client research turns up nothing, the skill relies on user-provided details and flags assumptions.
What it helps with
- draft an SOW from a project brief
- define deliverables and their acceptance criteria
- connect milestones to payment triggers
- document project risks and change procedures
- spot missing details before drafting an SOW
Example prompts for the agent
- Draft an SOW from this brief and save it as
sow.md. - Turn this project outline into an SOW with deliverables, milestones, and payment terms.
- Review this brief and ask me for details needed to prepare an SOW.
How to install sow-generator
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill sow-generator -a claude-code2Manually: put the files in place
~/.claude/skills/sow-generator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sow-generator/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill sow-generator -a codex2Manually: put the files in place
.agents/skills/sow-generator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill sow-generator -a cursor2Manually: put the files in place
.cursor/skills/sow-generator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills sow-generator2Manually: put the files in place
.github/skills/sow-generator/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill sow-generator -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path sow-generatorManually: put the files in place
.devin/skills/sow-generator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill sow-generator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about sow-generator
How do I install sow-generator in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill sow-generator -a claude-code. The skill file is at ~/.claude/skills/sow-generator/SKILL.md.
What does sow-generator do?
It drafts a Statement of Work from a project brief, covering scope, deliverables, milestones, pricing, and related terms across 16 sections.
How does the skill handle gaps in a project brief?
It requests required details and asks follow-up questions when the scope could be interpreted in materially different ways. It does not guess critical commercial terms.
Source text
SKILL.md · MIT
--- name: sow-generator description: Generates professional Statements of Work from a project brief. Use when a user needs to create an SOW, scope a project, define deliverables and milestones, or produce a consulting engagement document. tools: Read, Write, Bash, WebSearch model: inherit --- # Statement of Work Generator Generate complete, client-ready Statements of Work from a project brief, meeting the standards of Big Four consulting firms, top-tier agencies, and enterprise procurement. Produce polished documents ready for client review with minimal edits, never rough drafts or templates with blanks. ## Contents - `references/required-inputs.md` -- inputs to gather and pre-generation client research - `references/document-structure.md` -- the 16-section SOW structure with templates for every section - `references/pricing-templates.md` -- fixed-price, time-and-materials, and retainer pricing models (Section 11) - `references/legal-terms.md` -- confidentiality, IP, warranties, liability, termination, and other legal clauses (Section 14) - `references/change-management.md` -- change request and change order process (Section 12) - `references/risk-management.md` -- risk register and escalation path (Section 13) ## Workflow 1. Gather the required inputs. Read `references/required-inputs.md`. If any required item is missing, ask for it explicitly. Do not guess at critical commercial terms. 2. Research the client. Use WebSearch per `references/required-inputs.md` to gather company overview, recent news, technology footprint, and regulatory environment. If research yields nothing, proceed on user-provided inputs and flag assumptions explicitly. Never fabricate company information. 3. Select the pricing model from `references/pricing-templates.md` based on engagement type (default: fixed-price). 4. Generate all 16 sections following `references/document-structure.md`, pulling Section 11 from pricing-templates, Section 12 from change-management, Section 13 from risk-management, and Section 14 from legal-terms. Replace every bracketed placeholder with real values from inputs and research. Leave brackets only where the user explicitly deferred. Mark gaps with `[ACTION REQUIRED: ...]`. 5. Enforce traceability: every deliverable traces to a scope item, every milestone references deliverables, every payment trigger references a milestone, and all cross-referenced IDs (D-, M-, DEP-, R-, CR-, CO-) are correct. 6. Verify against the quality checklist below, then write the finished SOW to `sow.md` in the working directory (or a user-specified path). ## Output Requirements - Comprehensive: typically 500-800 lines for a standard engagement, longer for complex multi-phase projects. - Clean Markdown with proper heading hierarchy, tables, and numbered lists. - Professional, precise, unambiguous third-person prose. Define any non-standard jargon on first use. - No emojis anywhere in the document. - Include a footer note that the document is a template and should be reviewed by qualified legal counsel before execution. Never provide legal advice. ## Quality Checklist Verify before finalizing: - All user-provided inputs are reflected accurately - Client research is incorporated into Background and Context - Every in-scope item has corresponding deliverables - Every deliverable has measurable acceptance criteria - Every milestone has a date, associated deliverables, and payment trigger (if applicable) - Out-of-scope section is specific to this engagement, not generic - Assumptions are realistic and comprehensive; dependencies have owners and deadlines - Risk register contains engagement-specific risks, not boilerplate - Payment schedule sums to the total engagement fee - Legal sections are complete and internally consistent - All cross-references resolve correctly - No placeholder brackets remain except those explicitly deferred by the user - Document reads as a cohesive narrative, not a filled-in template - Tone is professional and consistent throughout ## Notes - For regulated industries (healthcare, finance, government), include industry-specific compliance sections (Section 15) and note additional legal review requirements. - Ask clarifying questions whenever the scope is ambiguous enough that the SOW could be interpreted in materially different ways. Ambiguity in an SOW is a professional failure.
© OneWave-AI · MIT · OneWave-AI/claude-skills