What problem does it solve? Turning a vague change request into an immediately implementable plan requires repo research, scoping discipline, and explicit verification criteria, which developers often skip or do inconsistently. ## Core Features & Use Cases - Bounded Planning: Researches the repository with local tools (rg, git status, targeted reads) and produces a plan listing every file, entity, action, and reason for a single bounded change. - Verification Contract: Every plan includes machine-checkable verification commands and testable acceptance criteria, with support for referencing roadmap goal IDs like EC-<ALIAS>-<N>. - Handoff & Manifest Integration: Writes plan artifacts, handoff files, reflections, and appends entries to plans/manifest.json via the phase_loop_runtime helpers. - Use Case: A developer asks for a plan to fix a specific bug; the skill inspects the relevant files, proposes the smallest coherent change set, documents docs impact, and lists the exact test commands that prove the fix. ## Quick Start Ask the agent to create a detailed implementation plan for a specific bug fix or small feature, for example: plan the change to add retry logic to the HTTP client module.
