aiskillstore/marketplace / skills/1102tools-dev/ot-project-description-builder
ot-project-description-builder
VerifiedTrigger for: OT project description, OTA scope, Research OT under 10 U.S.C. 4021, Prototype OT under 10 U.S.C. 4022, follow-on production scope under 10 U.S.C. 4022(f), milestone-based project scope, prototype objective, phase or go/no-go structure, BAA white-paper conversion, SOO conversion, transition planning, or scope reduction before OT cost analysis. Produce a milestone-based .docx plus a separate chat-only handoff to OT Cost Analysis. Use TRL only when the project supports it. Never place cost estimates, funding profiles, contribution calculations, prices, or skill-routing content in the document. Do NOT use for a FAR SOW/PWS, OT cost analysis, IGCE, agreement terms and conditions, or an Agreements Officer's authority, participant-status, successful-completion, or follow-on determination.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.4 KB |
| agents/openai.yaml | config | 266 B |
| references/authority-and-scope-rules.md | markdown | 4.6 KB |
| references/document-specification.md | markdown | 5.1 KB |
| references/handoff-specification.md | markdown | 2.1 KB |
| references/question-blocks.md | markdown | 3.3 KB |
| references/runtime-adaptation.md | markdown | 1.7 KB |
| references/validation-gates.md | markdown | 2.5 KB |
| scripts/validate_docx.py | script | 10.7 KB |
| skill-report.json | config | 36.5 KB |
| test.md | markdown | 4.7 KB |
| testing.md | markdown | 11.7 KB |
references/document-specification.md
View on GitHub# OT Project Description Specification
Use a supplied agency or consortium template as the design and section authority. Without one, use US Letter portrait, 1-inch margins, a restrained formal-business style, page numbers, real Word styles, and a dynamic Table of Contents when the document has more than eight main sections.
## Front matter
- Project title
- `Other Transaction Project Description`
- Government organization and performer, or `To Be Determined`
- Agreement number placeholder
- Authority as user-confirmed
- Version and date
- Distribution or handling marking only when supplied
Do not include the milestone handoff, price, cost, funding, staffing, or routing information.
## Section order
Use this relative order. A supplied template may rename or renumber sections, but it must preserve their functions.
### 1. Agreement Overview
- Purpose and project type
- User-confirmed statutory authority
- Parties and agreement structure
- Authority, participant-status, contribution, or follow-on facts marked `PENDING` when unresolved
### 2. Technical Background and Current State
- Problem or operational need
- Existing capability and evidence
- Prior work and present maturity
- Why this project is needed, without making the legal vehicle-selection determination
### 3. Project Objectives
For each objective state the capability, threshold, environment, verification method, and related completion evidence. Use TRL only when supported.
### 4. Technical Approach by Phase
For each phase state objective, entry conditions, duration, intended outcomes, risks retired, dependencies, and phase-exit criterion. Preserve performer flexibility unless the Government intentionally prescribes a method.
### 5. Milestone Schedule
Use one table:
`Milestone ID | Phase | Description | Deliverables Due | Completion Criteria | Timing or Sequence | Payment Type`
- Use the approved IDs and sequence.
- `Payment Type` is Fixed, Cost-Type, Mixed, or `PENDING` only when supplied.
- Completion criteria must identify objective evidence and acceptance responsibility.
- Do not include payment amounts, estimated labor, rates, ceilings, funding, or contribution arithmetic.
### 6. Deliverables
Use:
`ID | Title | Format | Due Trigger | Acceptance Criteria | Rights Category`
Due Trigger references a milestone or event, not an invented date. Include only deliverables mapped to project objectives, governance, or transition.
### 7. Data Rights
Separate background from agreement-generated material and state the supplied license posture by deliverable category. State markings, delivery format, Government uses, and unresolved negotiations. Do not present FAR or DFARS clauses as controlling unless incorporated.
### 8. Period of Performance
State total period, phase durations, sequencing, external dependencies, and the effect of go or no-go decisions. Use dates only when supplied.
### 9. Government Responsibilities
State Government-furnished property, information, facilities, systems access, test resources, review roles, and availability dates. Use `None identified` only when confirmed.
### 10. Key Personnel
State only roles, minimum qualifications, responsibilities, and substitution process. Do not include staffing counts, FTE, labor hours, SOC codes, or rates.
### 11. Reporting and Oversight
State technical reviews, status and risk reporting, milestone-review process, issue escalation, records, and acceptance roles.
### 12. Contribution Arrangement, when applicable
State the user-approved authority context, ratio, cash or in-kind treatment, valuation method, tracking, and source. Do not include dollar amounts, Government obligations, funding profiles, or calculations. Do not say the arrangement guarantees a follow-on.
### 13. Production Follow-On Provisions, when applicable
State transition planning and the user-supplied predecessor, selection, and completion facts. Make all follow-on language conditional on the Agreements Officer's determination. Do not promise award, require an invented TRL, or state that 4022(d) applies to the follow-on.
### 14. Constraints and Assumptions
Use:
`ID | Assumption or Constraint | Basis | Owner | Closeout Trigger`
Every `[TBD]` elsewhere in the document must have a matching row that names the owner and a concrete closeout action such as agreement modification, milestone review, or written Agreements Officer confirmation.
## Language and construction
- Use `The performer shall demonstrate...`, `The prototype shall achieve...`, and `The Government will provide...` when those obligations are approved.
- Use `Agreements Officer`, not `Contracting Officer`, unless a source template intentionally uses another title.
- Avoid CLIN, QASP, AQL, option-year, task-order, and FAR-clause language.
- Use real Heading 1, 2, and 3 styles, real lists, explicit table widths and cell margins, repeating table headers, and no fixed row heights.
- Keep headings with following content and prevent rows from splitting when practical.
- Use a page-number field and set Word to update fields on open.
- Do not place prompts, tests, skill names, file paths, internal workpapers, or tool instructions in the document.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |