plan-flow

# Plan Flow ## Overview Use this skill when the user needs: - A complete analysis of duplicated/redundant design in a codebase. - A detailed TODO plan with explicit file-level steps. - Strict execution evidence: change one step, test it, then update plan status. This skill is repository-agnostic. It defines how to analyze and plan, not only what was done in one specific repo. ## When to Activate - The canonical router resolved the task to `plan_first`. - The user needs a durable `plan/*.md` artifact with file-level steps and evidence. - The work requires duplicate/redundant design analysis before edits. ## Red Flags - A plan step lacks exact files, symbols, or verification commands. - Execution starts from a `clarify_first` situation with unresolved boundaries. - Multiple plan items are completed without updating status and evidence. ## Checklist - [ ] Capture baseline branch, dirty state, constraints, and known blockers. - [ ] Convert every finding into a scoped step with owner and validation. - [ ] Keep exactly one plan item in progress and update it before moving on. ## Routing Contract Integration Plan Flow owns the task only after the canonical router in [`workflows/references/routing-contract.md`](../references/routing-contract.md) resolves to `plan_first`. Route into Plan Flow when these readiness signals are true: - ambiguity has already been resolved - execution should not start directly - the task needs a durable `plan/*.md` artifact, phased sequencing,...