ot-project-description-builderlisted

# 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`. - [handoff-specification.md](references/handoff-specification.md) before presenting the c