improve-plan

Improve Plan

Use this workflow to strengthen an existing feature plan in a single fluid pass.

Critical Constraints

• NO IMPLEMENTATION: You are strictly FORBIDDEN from modifying any project source files. Your ONLY permissible write action is updating the existing Feature Plan document.
• CONTENT PRESERVATION (two-tier):

  • Factual context — NEVER delete. Goal statements, product scope, requirements, constraints, environment details, and problem/background analysis must be preserved verbatim. This includes product scope explicitly stated in the plan's Goal or Problem Description — you must not narrow or remove supported scenarios (e.g. multi-root workspaces) even if the current session is single-repo. If you believe a goal or scope statement is wrong, flag it in chat for the user — do not unilaterally correct it.

  • Reasoning outputs — correct with audit marking. Conclusions, chosen approaches, design decisions, and code examples may be corrected or replaced when the improve pass produces a better alternative. Every correction MUST be marked with a superseded callout so the change is auditable:

    Superseded: Reason: Replaced with:

    Never silently delete a conclusion and write a new one in its place. The callout is the audit trail — without it, the change is a protocol violation.

• SESSION vs PRODUCT SCOPE: Session directives (e.g. "single-repo", "skip compilation", "skip tests") constrain HOW you verify and organize the plan, not WHAT the plan covers. Do not conflate repo structure constraints with product feature requirements. If the plan targets multi-root workspaces, you must preserve and improve that scope regardless of the current session's repo configuration. Never transcribe a session directive into the plan file — not as a note, a caveat, or an explanation of what this run did or did not do. It binds you, not the reader. Written down it inverts: a later coder reads a constraint on the planner as an instruction to itself, and follows the document over the live dispatch that contradicts it.
• SINGLE PASS: Complete enhancement, dependency checks, the architecture challenge (Step 4), adversarial critique, balanced synthesis, and plan update in one continuous response.