What problem does it solve? Plans that only describe steps leave the executing agent to decide when work is done, causing scope drift and premature declarations of completion. This Skill produces plan files that define done through verifiable criteria, explicit out-of-scope rules, and stop-and-ask gates that survive context compaction and session restarts. ## Core Features & Use Cases - Completion contract in every plan: Each plan includes numbered Done means criteria checkable by a specific command or observation, plus Constraints and stop-and-ask gates. - Recon-grounded writing: Verifies every referenced path, filename, branch, and command against the actual repo before writing, and flags non-homogeneous scope for the user to split. - Fresh-session executability: Self-tests the plan so a session with zero conversation history can execute it from the file alone, making it directly consumable by goal runners or buildme. - Use Case: Ask for an implementation plan for a multi-file refactor; receive a dated plan file in the project's plans directory with ordered work items, exclusions, and a verification section with exact commands. ## Quick Start Ask the agent to write an implementation plan for your next feature, for example by saying write a plan for adding OAuth login to the app.
