ot-project-description-builder

Solid

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.

Data & Documents 25 stars 5 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
47
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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: 1. One project-description `.docx` suitable for the agreement file. It contains no cost estimate, should-cost, labor rate, milestone amount, funding profile, Government budget, or pricing conclusion. 2. One `MILESTONE HANDOFF TABLE` in 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](references/authority-and-scope-rules.md) before stating authority, participant status, contribution treatment, prototype scope, or follow-on provisions. - [question-blocks.md](references/question-blocks.md) when collecting or confirming inputs. - [document-specification.md](references/document-specification.md) in full before building the `.docx`. - [professional-product-standard.md](references/professional-product-standard.md) before ...

Details

Author
1102tools-dev
Repository
1102tools-dev/federal-contracting-skills
Created
5 months ago
Last Updated
1 weeks ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

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. 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.

3 Updated 2 weeks ago
1102tools-dev
Web & Frontend Listed

ot-project-description-builder

Build milestone-based project descriptions for Other Transaction (OT) agreements under 10 USC 4021/4022. Produces the agreement attachment that replaces a SOW/PWS in OT prototype and production follow-on contexts. Structures work around TRL progression phases (design, build, test, demonstrate) with milestone payment schedules tied to technical deliverables. Trigger for: OT project description, OTA project description, other transaction agreement, prototype agreement, OT scope, 10 USC 4021, 10 USC 4022, prototype OT, production follow-on OT, TRL-based project description, milestone-based scope, write an OT project description. Also trigger when user needs a project description before an OT cost analysis or has a BAA white paper/SOO to develop. Never contains cost estimates, funding profiles, or cost-sharing calculations. Do NOT use for SOW/PWS (use sow-pws-builder), OT cost analysis (use OT Cost Analysis), or FAR Part 15 requirements.

25 Updated 1 weeks ago
1102tools
AI & Automation Listed

ot-cost-analysis

Trigger for: Other Transaction or OT should-cost, cost estimate, cost-share analysis, milestone pricing, funding profile, proposed-price comparison, prototype price analysis, research OT budget, production follow-on OT estimate, or OT price-reasonableness support under 10 U.S.C. 4021 or 4022. Build auditable milestone-based .xlsx workbooks using BLS OEWS wages, CALC+ positioning, GSA Per Diem, materials, cost sharing, and agreement-specific fees. Use for pre-solicitation budgets and proposal comparisons. Do NOT use for FAR-based IGCEs, OT project descriptions, grants, or an Agreements Officer's determination. Requires the bls-oews, gsa-calc, and, when travel applies, gsa-perdiem MCP servers.

3 Updated 2 weeks ago
1102tools-dev