sow-pws-builderlisted

Build Statements of Work (SOW) or Performance Work Statements (PWS) for federal contracts through a structured scope decision workflow that produces a contract-file-ready .docx and a separate chat-only staffing handoff table for the IGCE Builder. Use this skill whenever the user asks to write a SOW, PWS, statement of work, performance work statement, convert a SOO to a SOW/PWS, develop requirements, define contract scope, build a work statement, or draft requirement language. Also trigger when the user says they need a SOW/PWS before building an IGCE, when they have a SOO and need to develop it into executable requirements, or when they need to reduce scope to fit a budget. The SOW/PWS document NEVER contains staffing tables, FTE counts, labor category counts, or IGCE-related content; that data lives in a separate chat-output handoff for the IGCE Builder skills (FFP, LH/T&M, CR). Do NOT use for IGCEs themselves (use IGCE Builder skills). Do NOT use for market research reports.
1102tools/federal-contracting-skills · ★ 25 · Data & Documents · score 79

Install: claude install-skill 1102tools/federal-contracting-skills

# SOW/PWS Builder ## Overview This skill walks a program office (or analyst acting on their behalf) through structured scope decisions and assembles the answers into a properly formatted SOW or PWS. The core insight: the program office doesn't need to know FTE counts or cost estimates up front — they need to make scope decisions, and staffing falls out as a derived output. **Outputs (TWO SEPARATE ARTIFACTS — never combined):** 1. **A .docx SOW or PWS** with standard federal sections — the contract file deliverable. This document contains NO staffing table, NO FTE counts, NO labor category counts, NO SOC codes, NO hours-per-year estimates, and NO IGCE-related content. FAR 37.102(d) requires the requirement to be described in terms of results, not hours or number of people performing the work. The one narrow exception is T&M/LH contracts, which get a Labor Category Ceiling Hours table in Section 5 per FAR 16.601(c)(2) — see Phase 2 Section 5 for details. 2. **A staffing handoff table** — an internal government workpaper presented in **chat output only** at the end of the skill run. This is the data handoff to the IGCE Builder skills (FFP, LH/T&M, CR). It is NEVER embedded in the SOW/PWS document. It is NEVER saved as a companion .docx or any other file. It exists solely as a markdown/code-block table in the conversation so the user can review it and the downstream IGCE Builder can consume it. **No external APIs required.** This is a decision tree + document generation ski