sow-pws-builderlisted

Trigger for: writing, revising, converting, or descoping a federal Statement of Work, Performance Work Statement, SOW, PWS, or SOO; develop executable requirements; define contract scope; create measurable performance standards; or prepare requirements before an IGCE. Produce a contract-file-ready .docx plus separate chat-only staffing and Section B handoffs. Never place FTEs, SOC codes, staffing estimates, IGCE content, CLINs, or pricing schedules inside the SOW/PWS body. Do NOT use for the IGCE, market research report, acquisition plan, QASP, or clause-selection matrix.
1102tools-dev/federal-contracting-agents · ★ 3 · AI & Automation · score 76

Install: claude install-skill 1102tools-dev/federal-contracting-agents

# SOW/PWS Builder ## Overview Turn program-office scope decisions into a contract-file-ready `.docx` SOW or PWS. Produce three separate outputs: 1. The SOW/PWS `.docx`, containing requirements and measurable acceptance or surveillance content. 2. A chat-only staffing handoff for the FFP, LH/T&M, or CR pricing skill. 3. A chat-only Section B handoff with suggested CLIN structure, labor categories or estimated hours when needed, travel/ODC lines, and the total ceiling-price input for T&M/LH. Never combine the handoffs with the document. FAR 37.602(b)(1) directs agencies, to the maximum extent practicable, to describe performance work by required results rather than method or hours. FAR 16.601 requires fixed hourly rates by labor category for T&M/LH and an overall ceiling price, but it does not require a labor-category ceiling-hours table inside the PWS. Keep pricing structure in Section B unless the user supplies a controlling solicitation template that places it elsewhere. No external MCP server is required. Load supporting files only when needed: - [question-blocks.md](references/question-blocks.md) for intake and scope questions. - [document-specification.md](references/document-specification.md) before authoring the `.docx`. - [regulatory-and-content-rules.md](references/regulatory-and-content-rules.md) for contract-type, security, QASP, and language rules. - [handoff-specification.md](references/handoff-specification.md) before final chat output. - [runtime-adaptati