update-plan

Skill: Update Plan

What This Skill Does

Keeps planning artifacts synchronized with actual progress:

• Updates todo items (mark done, add new items, note blockers)
• Updates phase status (pending → in_progress → completed)
• Updates plan status and changelog
• Updates implementation plan if approach changed during work
• Prepares for next phase when current phase completes

When to Use

• During work on a plan phase: to track progress in real-time
• After completing work: to mark items and phases as done
• When blockers are discovered: to document them
• When the implementation approach changes: to update the implementation plan
• After a plan review: to apply accepted Remove / Merge / Simplify findings while keeping scope artifacts consistent
• When the user asks to "update the plan" or "mark phase as done"

Execution Model (Recommended)

• Preferred: the primary agent runs this skill and updates artifacts under plans/<name>/.
• Rationale: plan updates encode session decisions and current intent; the primary has the best access to that context.
• Use doc-explorer only if verifying acceptance criteria requires codebase analysis (results are written to docs/).
• Optional (edge cases): delegate mechanical edits (bulk todo moves, large reshuffles) to doc-explorer if needed.

Routing Matrix (Who does what)

• Writes: updates under plans/<name>/ including plan.md, todo.md, phases/**, and (when needed) implementation/**.
• Primary: preferred owner for updates (session decisions/intents live here).
• doc-explorer: optional helper for mechanical edits or codebase analysis to verify acceptance criteria.
• implementer: never used for plan maintenance.

Workflow

Step 1: Identify the Plan

Find the active plan:

• Check plans/ directory for existing plans
• If multiple plans exist, use the question tool to ask the user which plan
• Read the plan's plan.md to understand the current status
• Read todo.md to see current task state