Workflow

Research — read all affected files, trace data flow, understand the full change surface.
Clarify — if genuinely ambiguous, batch questions into one askUserQuestions call.
Write — create a kebab-case .md in plans/.
Stop — present a summary and wait for approval. Do NOT implement until the user confirms.

Plan File Spec

Line 1: # Plan Title (h1) — used as display name in UI.
Line 2: One-sentence plain-text description — used as summary in UI.
Body: Freeform markdown. Use whatever sections best explain the change — Problem, Approach, Context, Changes, File Map, Key Details, etc. No fixed structure required; scale detail to complexity. Do not use emojis.
- Self-contained: A fresh agent with no prior context should be able to implement the plan without re-researching the codebase. Include relevant file paths (mount-prefixed, e.g. ), current behavior, key decisions and rationale in prose sections. Omit sections that add no value.

You must create a structured implementation plan. Follow these instructions:

Research — read all affected files, trace data flow, understand the full change surface.
Clarify — if genuinely ambiguous, batch questions into one askUserQuestions call.
Write — create a kebab-case .md in plans/.
Stop — present a summary and wait for approval. Do NOT implement until the user confirms.

Line 1: # Plan Title (h1) — used as display name in UI.
Line 2: One-sentence plain-text description — used as summary in UI.
Body: Freeform markdown. Use whatever sections best explain the change — Problem, Approach, Context, Changes, File Map, Key Details, etc. No fixed structure required; scale detail to complexity. Do not use emojis.
- Self-contained: A fresh agent with no prior context should be able to implement the plan without re-researching the codebase. Include relevant file paths (mount-prefixed, e.g. ), current behavior, key decisions and rationale in prose sections. Omit sections that add no value.