Implement an already-approved plan through an orchestrated, independently-reviewed build-and-revise loop. Use this after a plan (not just an instruction) exists and the user wants it built — "implement the plan", "execute the approved plan", "carry out the plan". The skill distills the plan into an executive plan, asks any clarifying questions, delegates the implementation to subagents (cheaper models for mechanical edits, stronger models for hard reasoning), has fresh-context subagents review the result, then loops — reconcile findings, re-align with the user, revise, re-review — until both the review and the user are satisfied. It is the counterpart to plan-changes. Prefer it over implementing inline whenever the change is non-trivial, spans multiple files or systems, or benefits from independent review.
Review Git staged changes for correctness risks and concrete maintainability, readability, and simplification opportunities without modifying files or rerunning tests. Use when asked to review the index, staged diff, pending commit, or pre-commit changes while assuming the test suite has already passed.
Orchestrate a thorough, independently-reviewed implementation plan for a set of changes before any code is written. Use this whenever the user wants to "plan a change", "design an approach", "figure out how to implement X", "write a plan", "think through" a feature, refactor, or migration, or asks for a well-researched plan they can review and approve. The skill explores the codebase with delegated subagents (cheaper models for simple lookups, stronger models for hard reasoning), asks as many clarifying questions as it needs, drafts a plan, has a fresh-context subagent critique it, revises, and presents the result through the plan tool for approval. Prefer this skill over planning inline whenever the change is non-trivial, spans multiple files or systems, or benefits from independent review — even if the user never says the word "plan".