What problem does it solve? When a task-scoped subagent is dispatched for a Control Tower slice, it arrives with zero context and cannot ask questions. This Skill turns the GitHub issue into a prescriptive plan that closes every decision (names, signatures, typed errors, constants, test names, exact commands) while leaving function bodies to test-driven development, so the plan passes the machine-checked plan-contract validation. ## Core Features & Use Cases - Fixed 9-section plan structure: Enforces a strict template with closed decisions, reference patterns, inventory, interfaces, test strategy, tasks, global verification, and assumptions. - Labelled code block taxonomy with budgets: Current state (12 lines), Contract (25 lines), Call site (10 lines), and Final text (12 lines) blocks, capped at 30 lines per task and 3500 characters per task. - Machine-checked literality and language rules: Every quoted current state must exist verbatim in the repo, verification commands must be exit-code predicates, and prose must follow Simplified Technical English rules validated by --check-plan. - Use Case: You are dispatched for issue #42 of a TypeScript monorepo slice. You read the issue and conventions, copy the plan template, write one task at a time running dispatch-check --check-plan after each, then commit the plan as the branch's first commit and post it as an issue comment. ## Quick Start Use the writing-plans-prescriptive skill to turn the dispatched Control Tower issue into a validated prescriptive slice plan before touching any production code.
