← ClaudeAtlas

ot-project-description-builderlisted

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.
1102tools/federal-contracting-skills · ★ 25 · Web & Frontend · score 79
Install: claude install-skill 1102tools/federal-contracting-skills
# OT Project Description Builder ## Overview This skill walks an agreements officer (AO) or program office through structured prototype scope decisions and assembles the answers into a milestone-based project description for an Other Transaction agreement. The core insight: OTs structure work around technology maturation phases and technical milestones, not task/subtask CLINs or performance objectives. The program office defines what must be demonstrated at each gate, and the performer proposes how to get there. **Outputs (TWO SEPARATE ARTIFACTS -- never combined):** 1. **A .docx project description** with milestone-based structure -- the agreement attachment. This document contains NO cost estimates, NO should-cost figures, NO funding profiles, NO cost-sharing calculations, and NO government budget data. It defines what the prototype must achieve, by when, and what constitutes success at each milestone. 2. **A milestone handoff table** -- an internal government workpaper presented in **chat output only** at the end of the skill run. This is the data handoff to the OT Cost Analysis skill. It is NEVER embedded in the project description document. It is NEVER saved as a companion file. It exists solely as a markdown table in the conversation so the user can review it and the downstream OT Cost Analysis skill can consume it. **No external APIs required.** This is a decision tree + document generation skill. **Statutory basis:** 10 USC 4021 (authority to carry out prototyp