skills.rest
BdM-15
BdM-15COMMUNITY
Explore all skills by this author →
GitHub

sow-pws-builder

Generate compliant DOCX statements of work or performance work statements with separate IGCE chat output.

Updated Apr 14, 2026
Search Tags:#acquisition#sow#contract-generation#federal-contracting#pws#scope-decision#igce-hand-off
One-click install
npx skills add https://github.com/BdM-15/shipley-bd-capture-skills --skill sow-pws-builder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sow-pws-builder
Source: https://github.com/BdM-15/shipley-bd-capture-skills/tree/main/govcon-skills/sow-pws-builder
Command: npx skills add https://github.com/BdM-15/shipley-bd-capture-skills --skill sow-pws-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about sow-pws-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a SOO into a SOW or PWS for a federal contract?▼

To convert a Statement of Objectives (SOO) into a SOW or PWS, you use a structured scope-decision workflow that guides phased inputs to generate a compliant .docx contract document. The process preserves staffing derivations separately for downstream IGCE analysis.

What is the best way to write a performance work statement without including staffing data?▼

Writing a performance work statement without staffing data requires guardrails that enforce separation of concerns, producing a compliant .docx document with no FTE counts or labor categories while outputting a separate chat-based staffing handoff for the IGCE Builder.

Can I reduce contract scope to fit a budget using a structured SOW workflow?▼

Yes, a structured SOW workflow supports scope reduction by guiding phase-structured decisions to determine what to cut from new work statements, ensuring the final contract document aligns with budget constraints while maintaining compliance.

Does the SOW document include IGCE or labor category data for federal contracting?▼

No, the SOW or PWS document never includes IGCE-related content, staffing tables, FTE counts, or labor categories. That staffing data lives in a separate chat-output handoff designed specifically for downstream IGCE Builder skills.

How do I start building a SOW from a rough concept for federal acquisition?▼

To build a SOW from a rough concept, provide your initial idea to the structured workflow, which will guide you through Phase 1 scope decisions to progressively develop executable requirements and generate a ready-to-award contract document.

When should I not use a SOW builder for federal contracting requirements?▼

You should not use a SOW builder for generating IGCEs themselves or for producing market research reports; use specialized IGCE Builder skills for pricing and a Market Research Builder for market analysis instead of generating work statements.

Related Skills

Explore More Legal & Compliance Skills→
lexicalninjalexicalninja

draft-section

Generate proposal-ready section prose from solicitation analysis and compliance matrices.

Community
Advanced
BdM-15BdM-15

igce-builder-lh-tm

Automate IGCE workbook creation for LH and T&M contracts using BLS OEWS, CALC+, and Per Diem data.

Community
Advanced
borgheiborghei
467

product-strategist

Analyze markets and generate strategy frameworks for product teams.

Community
Basic
BdM-15BdM-15

igce-builder-ffp

Build Firm-Fixed-Price Independent Government Cost Estimates with layered wrap-rate models.

Community
Advanced