What problem does it solve? Planning a small, single-concern code change often gets either skipped entirely or buried under heavyweight roadmap tooling. This Skill produces a concrete, immediately implementable plan document for one bounded change — a bug fix, small feature, or targeted refactor — without the overhead of a full phase roadmap pipeline. ## Core Features & Use Cases - Parallel repo reconnaissance: Launches Explore subagents to map existing code, reusable patterns, and hidden coupling before proposing any change. - Explicit change enumeration: Every planned change names the file, entity, action, and reason, with modification-over-creation and scope-discipline rules enforced. - Verification and acceptance criteria: Requires runnable shell/test commands and testable acceptance assertions, plus an explicit documentation-impact decision. - Optional external review: With --review-external, the plan is critiqued by Gemini and Codex CLIs via a shared review script. - Reflection and handoff closeout: Writes a repo-agnostic reflection and a repo-specific handoff so a fresh implementer session can pick up the plan safely. - Use Case: You need to add a refresh-token endpoint to an existing auth module. Invoke the Skill with the task description; it researches the codebase, writes a plan to .consiliency/plans/, commits it, and leaves a validated handoff for the implementing session. ## Quick Start Ask the agent to plan a bounded change, for example: run claude-plan-detailed with the task "fix stale cache eviction in the session store" and it will research the repo and write an implementable plan document.
