ot-project-description-builder
Trigger 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.
Install / Use
npx skills add aiskillstore/marketplace --skill ot-project-description-builderInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
DesignSupported Platforms
Tags
Our assessment of ot-project-description-builder
ot-project-description-builder scores 84/100 on our quality scale, 202nd of 270 Design skills we index.
Its SKILL.md is 12 KB long, well organised into 15 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 428 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ot-project-description-builder is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ot-project-description-builder compared with similar skills
All 4 of these similar skills score higher than ot-project-description-builder; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ot-project-description-builder (this skill)by aiskillstore | 84 | 428 | 56d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 58d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 58d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 8d ago | SKILL.md |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 8d ago | SKILL.md |
Frequently asked questions
- How do I install ot-project-description-builder?
- Run
npx skills add aiskillstore/marketplace --skill ot-project-description-builder. The install tabs above show the steps for each supported agent. - Which AI agents does ot-project-description-builder work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ot-project-description-builder safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ot-project-description-builder still maintained?
- The repository was last updated about 2 months ago, so ot-project-description-builder is actively maintained.
Skill content
View source on GitHubname: ot-project-description-builder description: > Trigger 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.
OT Project Description Builder
Purpose and operating boundary
Create a milestone-based .docx project description for a Research OT under 10 U.S.C. 4021, Prototype OT under 10 U.S.C. 4022, or a follow-on production action under 10 U.S.C. 4022(f). Define the technical outcome, phase logic, deliverables, completion evidence, Government responsibilities, and agreement-specific controls without making the Agreements Officer's authority, participant-status, successful-completion, or follow-on-eligibility determination.
Produce two separate outputs:
- One project-description
.docxsuitable for the agreement file. It contains no cost estimate, should-cost, labor rate, milestone amount, funding profile, Government budget, or pricing conclusion. - One
MILESTONE HANDOFF TABLEin chat after document validation. It is an internal workpaper for OT Cost Analysis and never a document section, appendix, or companion file.
No external API is required.
Reference map
Load only what the active workflow needs:
- authority-and-scope-rules.md before stating authority, participant status, contribution treatment, prototype scope, or follow-on provisions.
- question-blocks.md when collecting or confirming inputs.
- document-specification.md in full before building the
.docx. - handoff-specification.md before presenting the chat-only milestone handoff.
- validation-gates.md before generation and again before delivery.
- runtime-adaptation.md when selecting input, document-generation, rendering, validation, or delivery capabilities.
Non-negotiable gates
- Correct authority: 10 U.S.C. 4021 covers basic, applied, and advanced research. 10 U.S.C. 4022 covers prototype projects. Section 4022(f) covers follow-on production contracts or transactions. Never label a prototype as a 4021 action.
- Authority is supplied, not selected: Explain the three paths when needed, but require the user or Agreements Officer to identify the authority. Do not default an uncertain request to Prototype OT.
- Correct prototype conditions: Under 4022(d)(1), Path A is significant participation by a nontraditional defense contractor or nonprofit research institution; Path B covers all significant non-Government participants being small businesses or nontraditional defense contractors; Path C requires at least one-third of total project cost from non-Federal sources; Path D is a senior procurement executive's written exceptional-circumstances determination. There is no Path D competition-commitment option.
- Status and contribution facts are not inferred: Do not decide nontraditional status, small-business status, significant participation, the applicable 4022(d) path, contribution ratio, contribution valuation, or fee. Record the user's approved facts and source. Research and follow-on production contribution arrangements are also supplied, not defaulted.
- TRL is optional: Use TRL only when supplied or genuinely useful. A prototype can address a proof of concept, model, process, agile development, novel commercial application, operational utility, or a combination. Do not force every project through a hardware-style TRL ladder.
- Milestones precede prose: Present the derived phase and milestone structure, including completion evidence and pending decisions, then end at the approval question. Do not generate the
.docxin the same response. - Artifact separation: Keep pricing, labor hours, contribution arithmetic, cost figures, funding, and skill-routing language out of the document. Keep the milestone handoff in chat only.
- Data rights are negotiated: Record the supplied posture by deliverable and distinguish background from agreement-generated material. Do not state that FAR or DFARS clauses control unless the agreement incorporates them.
- Follow-on language stays conditional: Record user-supplied predecessor, competitive-selection, and successful-completion facts without deciding eligibility. Do not promise award or say 4022(d) is a follow-on requirement.
- Every placeholder closes: Each
[TBD]must name an owner, trigger, and disposition method in Constraints and Assumptions. - Independent document validation: Run the bundled validator, render the document, inspect every page, fix defects, and repeat. Do not treat DOCX creation alone as proof of usability.
Pre-flight: capabilities and inputs
- Inspect attached source documents with the host's native document or PDF reader. Preserve explicit decisions and identify contradictions instead of silently resolving them.
- Require a
.docxauthoring path, Python 3.10 or later withpython-docxfor the bundled validator, and a rendering path such as LibreOffice when available. - Use an agency or consortium template when supplied. Otherwise use the formal document baseline in the document specification.
- Confirm that a source document's prices, rates, CLINs, budgets, and funding values will be excluded. Record only that excluded pricing data exists; the user can provide it separately to OT Cost Analysis with a confirmed amount basis.
- If document generation or rendering is unavailable, stop before promising a validated artifact and report the missing capability.
Select a workflow
Workflow A: build from a concept
Use when the user supplies an objective, problem, requirement, or early concept but no approved milestone structure.
Workflow B: convert an existing document
Use for a white paper, proposal abstract, SOO, SOW, draft project description, or similar source. Extract settled technical facts; remove FAR clause, CLIN, QASP, staffing, and pricing content from the project-description artifact. Do not re-ask settled questions.
Workflow C: revise or reduce scope
Use when an existing project description or approved milestone structure must be changed. Preserve unaffected decisions, identify the technical and schedule effect of each proposed deletion or deferral, and obtain approval for the revised milestones before editing the document.
Stage A: authority and acquisition frame
Read authority-and-scope-rules.md and collect only missing items:
- User-confirmed authority: 4021 research, 4022 prototype, or 4022(f) follow-on production
- For a prototype, user-confirmed 4022(d)(1) Path A, B, C, or D and source
- Participant and significant-participation facts as confirmed by the Agreements Officer
- Approved contribution arrangement and source, or
PENDING - Direct or consortium structure and any controlling template
- Project purpose, present technical or operational baseline, and source documents
- For follow-on production, predecessor prototype and user-supplied selection and completion facts
Use the host's structured question tool when available. Otherwise use numbered questions and accept numbers, labels, or free text. If authority is uncertain, explain the differences neutrally and end at the authority question. Do not continue to scope derivation.
When required authority items are complete, show a short authority record and ask the user to confirm or correct it. End at that question.
Stage B: scope and milestone decisions
After Stage A approval, read question-blocks.md. Collect missing scope inputs in related batches:
- Outcome and measurable success conditions
- Existing baseline and major risks
- Phase logic, schedule, and external dependencies
- Test, demonstration, or acceptance environment
- Systems, interfaces, prototype units, data, and security boundaries
- Deliverables and objective completion evidence
- Data-rights posture by deliverable category
- Government-furnished property, information, facilities, and personnel
- Key roles, reviews, reporting, off-ramps, and transition intent
Use TRL only when supported. Otherwise describe maturity through observable baseline, target capability, and completion evidence.
Derive a candidate structure with:
Milestone ID | Phase | Objective | Estimated Duration | Deliverables | Completion Evidence | Timing or Sequence | Payment Type | TRL In/Out | Notes
Payment Type remains PENDING unless supplied. Do not infer Fixed, Cost-Type, or Mixed from milestone wording.
Decision Summary gate
Present:
- The confirmed authority record
- Explicit user decisions
- Derived assumptions and their rationale
- Pending items and their owner
- The full candidate milestone table
Ask the user to confirm, amend, or reject the structure. End immediately after that question. A request to skip questions does not waive this gate unless the user explicitly approves the displayed structure.
Build the project description
After approval:
- Read document-specification.md and validation-gates.md in full.
- Apply the supplied template or the formal baseline. Use real Word heading styles, lists, tables, page-number fields, and a dynamic TOC when required.
- Preserve approved milestone IDs, phase relationships, deliverables, completion evidence, timing, payment-type status, and user overrides.
- Carry each phase-exit criterion into both the Technical Approach by Phase section and the corresponding Milestone Schedule row.
- Include a Contribution Arrangement section only when an approved arrangement affects the agreement. State ratios and cash or in-kind treatment without dollar amounts or funding calculations. Label pending facts.
- Include Production Follow-On Provisions only when the user requests them. State conditions and transition planning without making an eligibility finding or promising an award.
- Keep the performer responsible for the technical approach unless the Government has intentionally prescribed a method.
- Save only the project-description
.docxas the document artifact.
Validate and deliver
- Run
scripts/validate_docx.py <document> --json. - Render the
.docxto page images with the available document renderer. - Inspect every page for clipping, overlap, broken tables, blank pages, bad page breaks, unreadable density, missing glyphs, placeholder leakage, and inconsistent hierarchy.
- Correct every failure, rerun the validator, rerender, and inspect again.
- State whether LibreOffice or Microsoft Word performed the render. Do not claim Word compatibility from LibreOffice alone.
- Read handoff-specification.md and emit the approved milestone handoff in chat. Never save it as a file or add it to the
.docx. - Report unresolved
[TBD]items, the source and date of authority facts, and any validation layer that could not run. - If the document contains a dynamic TOC, tell the user: `Open the document in Word, press Ctrl+A (Cmd+A on Mac), then F9 (or Fn+F9) to update all fields and page n
Truncated for display — read the full file on GitHub.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse 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 em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
