What problem does it solve? Turning a bug fix, small feature, or targeted refactor into a concrete, immediately implementable plan is error-prone: plans often stay vague, miss documentation impact, or lack testable acceptance criteria. This Skill researches the repository and produces a bounded, file-by-file implementation plan that a single developer or agent can execute end to end. ## Core Features & Use Cases - Bounded change planning: Enumerates every change by file path, entity, action, and reason, and recommends splitting work that exceeds roughly 8 source files or 3 distinct concerns. - Research-first workflow: Gathers context via git status, git log, and targeted ripgrep reads, with optional explorer subagents, and forbids proposing changes to files that were not located. - Verification contract: Requires machine-checkable verification commands and testable acceptance criteria, optionally referencing roadmap goal IDs like EC-<ALIAS>-<N>. - Closeout artifacts: Writes a plan document, a repo-local handoff with consumer-validation frontmatter, a run reflection, and a plans/manifest.json entry. - Use Case: Ask for a plan to fix a stale cache eviction bug; the Skill inspects the relevant modules, then writes plans/detailed-fix-stale-cache-eviction-<timestamp>.md with changes, docs impact, verification commands, and acceptance criteria. ## Quick Start Ask the agent to create a detailed implementation plan for your specific bug fix or small feature, for example: plan a detailed change to add a refresh token endpoint to the auth module.
