plan

What problem does it solve? Agents often write plans that are ignored, guessed at, or drift from reality during implementation. This Skill forces a real implementation plan to exist before any code is touched, grounding every claim in the actual repository and gating execution phase by phase. ## Core Features & Use Cases - Codebase-grounded planning: Reads AGENTS.md, context maps, and the actual implementation so every file path and API in the plan is verified, not recalled. - Phased plans with verification gates: Splits larger work into ordered phases, each ending in a gate that must pass before the next phase starts, with a Task Ownership table for concurrency and risk classification. - Structured user questioning: Uses a strict question format (references/question-format.md) to resolve real unknowns before writing, recording all answers in the plan's Decisions section. - Use Case: Before implementing a new API endpoint, invoke the skill to inspect the repo, grill you on open design questions, and produce a plan saved to ~/.agents/plans/<repo>/ with contracts, pre-mortem scenarios, and validation steps. ## Quick Start Ask the agent to plan the feature you want to build, for example by saying "write a plan for adding user authentication to the settings page".