sow-pws-builder

What problem does it solve?

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 and need to know what to cut. 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 (use Market Research Builder).

Core Features & Use Cases

• Structured intake and phased workflows (SOO-to-SOW/PWS conversion, Full Build, and Scope Reduction)
• Document generation of a compliant .docx SOW/PWS with standard sections
• Separate chat-based IGCE handoff data handoff for downstream pricing skills
• Guardrails to ensure No staffing tables or FTE data appear in the final document
• Use Case: Convert a SOO into a ready-tobe-awarded SOW/PWS while preserving staffing derivations for IGCE analysis in chat

Quick Start

Provide a rough concept or SOO, and let the skill guide you through Phase 1 decisions to generate a SOW or PWS.