sow-pws-builderlisted

# 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. ## Product quality default Make the PWS/SOW read like a concise acquisition-file deliverable, not a process transcript. Its first page must identify the mission need, the performance decision it supports, the material operating assumptions, and the next acquisition-team action. Use a requirement-specific title, a short executive purpose block, and distinct visual hierarchy appropriate to the document type. Put detailed evidence and source notes in a compact appendix