Skip to content

aiskillstore/marketplace / skills/1102tools-dev/sow-pws-builder

sow-pws-builder

Verified

Trigger for: writing, revising, converting, or descoping a federal Statement of Work, Performance Work Statement, SOW, PWS, or SOO; develop executable requirements; define contract scope; create measurable performance standards; or prepare requirements before an IGCE. Produce a contract-file-ready .docx plus separate chat-only staffing and Section B handoffs. Never place FTEs, SOC codes, staffing estimates, IGCE content, CLINs, or pricing schedules inside the SOW/PWS body. Do NOT use for the IGCE, market research report, acquisition plan, QASP, or clause-selection matrix.

references/document-specification.md

View on GitHub
# SOW/PWS Document Specification

Use a supplied agency template as the design and section authority. Without one, use US Letter portrait, 1-inch margins, a restrained formal business style, page numbers, and real Word styles.

## Front matter

- Plain title paragraph, document type, requirement title, agency or office, solicitation/contract placeholder, version/date, and distribution marking when supplied.
- Dynamic Table of Contents after the title block for documents with more than eight main sections.
- Do not include a staffing, pricing, IGCE, or Section B summary in front matter.

## Section order

Preserve this order. Renumber when an agency template requires it, but do not merge unrelated sections.

### 1. Introduction

- Purpose
- Background
- Scope summary
- Applicable documents and standards
- Confirmed contract framework only when it changes performance obligations; for CPFF, state the confirmed Completion or Term form

### 2. Definitions and Acronyms

Define terms that materially affect performance. Omit common terms that do not need contractual definition.

### 3. Requirements

For an SOW, organize by task area:

- Task number and title
- Contractor action
- Subtasks or sequence only when Government-directed method is necessary
- Deliverables
- Government-furnished resources

For a PWS, organize by performance objective:

- Objective number and title
- Required outcome
- Performance standard
- AQL
- Assessment method
- Contract-administration consequence or incentive when applicable

Do not state FTE, staffing count, SOC, annual labor hours, proposed rate, CLIN, or price.

### 4. Deliverables

Use a table only because deliverables are repeated comparable records:

`ID | Title | Description | Format | Frequency | Due Date or Trigger | Acceptance Criteria | Approving Role`

Include transition, status, system documentation, training, or final artifacts only when the scope requires them. Do not add generic deliverables that have no mapped requirement.

### 5. Period of Performance

State base, options, phase boundaries, mobilization, and extension placeholders supplied by the user. Do not include Section B CLIN numbering.

### 6. Place of Performance

State sites, remote-work boundaries, travel destinations, access hours, and Government facility constraints. Do not infer duty locations.

### 7. Government-Furnished Property and Information

Identify each item, availability, condition, access date, maintenance responsibility, and return/disposition requirement. State `None identified` only when the user confirms it.

### 8. Security and Privacy

Tailor to the confirmed information and facility context. Address safeguarding, CUI/privacy, suitability, clearances, facility requirements, incident reporting, access termination, and agency-specific authorities. Do not invent classification or clearance.

### 9. Key Personnel

Name roles, minimum qualifications, certifications, substitution notice, and approval process. Do not include number of people, FTEs, SOCs, hours, or the full labor-category list.

### 10. Reporting and Oversight

State report content, cadence, meetings, data sources, Government roles, escalation, and record retention. Avoid duplicating the Deliverables table.

### 11. QASP Summary or Inspection and Acceptance

- PWS: title `QASP Summary`; use metric, standard, AQL, method, frequency, and payment/administrative consequence.
- SOW: title `Inspection and Acceptance`; use deliverable, criterion, method, review period, approving role, and remedy.

Do not map thresholds to CPARS ratings.

### 12. Transition

- Transition-in: incumbent cooperation, knowledge transfer, access, inventory, parallel operation, readiness, and acceptance.
- Transition-out: data and property return, documentation, successor support, access termination, and schedule.

### 13. Constraints and Assumptions

Use:

`ID | Assumption or Constraint | Basis | CO or Program Office Action`

Prefix derived defaults with `[DEFAULT]`. Record pending contract type, commerciality, CPFF form, security, Government data, volume, or other unresolved decisions. Do not hide assumptions in narrative.

## Appendices

Use only when applicable:

- Current environment
- Historical workload and volume
- System interfaces
- Acronyms

Never create an appendix for staffing, FTE allocation, IGCE handoff, CLIN structure, pricing, or estimated labor hours.

## Language

- SOW: `The Contractor shall <specific action>.`
- PWS: `The Contractor shall achieve, maintain, or ensure <measurable result>.`
- Avoid standalone `support`, undefined `as needed`, unnamed `best practices`, and coordination with no required outcome.
- Every requirement must be testable through inspection, demonstration, analysis, test, or an identified performance record.
- Use `Contracting Officer`, `Contracting Officer's Representative`, and `Program Office` consistently.

## DOCX construction

- Real Heading 1, 2, and 3 styles.
- Real numbered and bulleted lists; no typed bullet characters.
- Explicit DXA table widths, cell margins, repeating header rows, and no fixed row heights.
- Keep headings with following content and repeat table headers across pages.
- Use page-number fields in the footer.
- Set update-fields-on-open for the TOC.
- Do not place internal instructions, test notes, prompt text, skill names, or file-system paths in the document.
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall