BdM-15/capture-insights / skills/subcontractor-sow-builder
subcontractor-sow-builder
VerifiedDrafts a federally-defensible SOW or PWS the prime issues to a subcontractor / teaming partner — same FAR 37.102(d) / 37.602 / 16.601(c)(2) / 16.306(d) discipline a contracting officer applies, opposite seat. USE WHEN the user asks to "write a SOW for our sub", "draft a PWS for [Partner]", "build the teaming-partner statement of work", "convert this SOO into a sub SOW", "we need a SOW the sub will sign", or any variant of authoring a downstream work statement. Walks the upstream 3-phase tree (acquisition intake → 6 scope blocks → 14-section assembly), pulls scope from the active Theseus KG (requirements, deliverables, work_scope_items, performance_standards), enforces FAR 37.102(d) "no FTEs in body", emits a chat-only staffing handoff for the prime's cost build, writes Markdown for `renderers` → .docx. DO NOT USE FOR prime proposal prose (`proposal-generator`), reverse-engineering an RFP (`rfp-reverse-engineer`), pricing the sub (`price-to-win`), or clause audit (`compliance-auditor`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.3 KB |
| UPSTREAM.md | markdown | 4.7 KB |
| evals/evals.json | config | 5.9 KB |
| references/decision_tree_blocks.md | markdown | 7.6 KB |
| references/far_citations.md | markdown | 9.4 KB |
| references/language_rules.md | markdown | 3.2 KB |
| references/sow_pws_section_structure.md | markdown | 10.1 KB |
references/language_rules.md
View on GitHub# Language Rules — SOW vs PWS Verb Patterns and Anti-Patterns
> Source: upstream `sow-pws-builder` Phase 2 Language Rules section. Mirrored verbatim for the prime → sub seat.
## SOW Language
**Pattern:** "The contractor shall [verb]..."
**Verbs:** prescriptive, task-oriented. Examples:
- The contractor shall **perform** monthly system patching across all production servers.
- The contractor shall **deliver** a quarterly system architecture review.
- The contractor shall **maintain** a configuration management database.
- The contractor shall **provide** Tier 2 user support during business hours.
## PWS Language
**Pattern:** "The contractor shall achieve / maintain / ensure..."
**Verbs:** outcome-oriented, measurable. Examples:
- The contractor shall **achieve** 99.9% system availability during business hours.
- The contractor shall **maintain** mean-time-to-resolve (MTTR) of less than 4 hours for Severity 2 incidents.
- The contractor shall **ensure** all CUI is handled in compliance with NIST SP 800-171.
## Anti-Patterns (avoid)
| Anti-pattern | Why it fails | Compliant alternative |
| ---------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------ |
| "Support" as a standalone verb | Too vague — support how? | Specify the deliverable or outcome being supported. |
| "As needed" or "as required" without defined trigger | CO retains unilateral discretion; sub cannot price the obligation | Define the trigger event, frequency, or threshold. |
| "Best practices" without citing a standard | Unverifiable; ghost requirement | Cite the specific standard (NIST, ISO, ITIL, etc.). |
| "Coordinate with" without specifying the deliverable or decision | Coordination is meeting overhead, not a requirement | Specify the deliverable, decision, or artifact that results. |
| Requirements that cannot be measured or verified | Untestable; contractor cannot demonstrate compliance | Add a measurable threshold, AQL, or method of assessment. |
## SMART Test (every requirement)
Each requirement in Section 3 must be:
- **S**pecific
- **M**easurable
- **A**chievable
- **R**elevant
- **T**ime-bound
If a requirement fails any of these, flag it during assembly and either rewrite or move to Section 14 as an open assumption.
## Document-Wide Discipline
- **No staffing language in the body.** No FTE counts, no SOC codes, no labor category counts, no hours-per-year. Even when describing prior-state scope reductions in Section 14, describe in CAPABILITIES AND COVERAGE, not staffing counts. FAR 37.102(d) governs.
- **No CLIN tables in the body.** CLINs live in the prime↔sub subagreement Section B (chat-only handoff at end of run).
- **Cite the specific FAR subsection.** Never bare `FAR 16.306`, `FAR 16.601`, `FAR 52.246` — always with the controlling subparagraph.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |