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/question-blocks.md
View on GitHub# Question Blocks
Ask only for missing facts. Use the host's structured question tool when available; otherwise use numbered questions with an `Other` or free-text path. Batch related items, but do not cross a required approval gate in the same response.
## Stage A: authority and acquisition frame
1. Which authority has the Agreements Officer identified: 10 U.S.C. 4021 research, 4022 prototype, or 4022(f) follow-on production?
2. For a prototype, which 4022(d)(1) path applies: A, B, C, or D? What is the source or determination status?
3. What participant-status and significant-participation facts has the Agreements Officer confirmed?
4. What contribution arrangement is approved, including ratio, cash or in-kind form, valuation, and source? Use `PENDING` when undecided.
5. Is the action direct or consortium-based? Is there a required template?
6. What source documents control the technical scope?
For a follow-on production action also ask for the predecessor prototype, selection facts, completion facts, and user-confirmed transition intent. Do not make the statutory findings.
## Stage B1: outcome and baseline
1. What problem or operational need must the project address?
2. What exists today, and what evidence supports that baseline?
3. What observable capability must exist at completion?
4. Which quantitative thresholds, environments, interfaces, or user conditions define success?
5. What major technical, operational, schedule, or integration risks must be retired?
If the user uses TRL, collect entry level, target level, supporting evidence, and the assessment owner. Otherwise use observable maturity statements.
## Stage B2: phases and milestones
For each phase or work segment collect:
- Objective and duration
- Entry conditions
- Required activity or outcome
- Deliverables
- Completion evidence and reviewer
- Go or no-go decision and off-ramp
- Dependencies and Government actions
- Payment Type supplied by the user, or `PENDING`
Each completion criterion must be specific, measurable, testable, and capable of an objective pass or fail decision. Avoid `satisfactory`, `as needed`, or `as determined by the Government` without a measurable test.
## Stage B3: agreement execution details
Collect only applicable items:
- Prototype units, software releases, datasets, models, interfaces, and test events
- Places of performance and Government test or demonstration environments
- Government-furnished property, information, systems access, and personnel
- Security, privacy, export-control, and controlled-information boundaries supplied by the user
- Data-rights posture by deliverable category
- Key roles and substitution process
- Review, reporting, risk, and issue cadence
- Transition intent and follow-on provisions
- Constraints, assumptions, unresolved thresholds, owners, and closeout triggers
## Scope-reduction choices
Show the consequence of each proposed reduction without estimating savings unless OT Cost Analysis supplies them. Useful levers include:
- Defer a phase or target capability
- Reduce prototype units or environments
- Narrow interfaces or user groups
- Combine reviews without weakening completion evidence
- Defer noncritical deliverables
For each option show what capability, evidence, risk retirement, schedule, or transition readiness is lost. Obtain approval for the revised milestone table before editing 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 |