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 user explicitly requests a durable convergence plan or the work is major architecture/migration scope. - 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 while a material product or safety choice is unresolved. - 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. ## Planning Boundary Plan Flow is for major architecture, migrations, durable convergence work, or an explicit user request. Ordinary bugs, docs, tests, and mechanical edits execute directly. The plan records outcome, boundaries, ordered steps, verification, and real blockers. It does not emit a routing object, runtime snapshot, lane map, or fixed exec...