Add "Replan" Action in Human Review Stage

[minhluan1590]

Feature Request: Add "Replan" Action in Human Review Stage

Summary

Add the ability to move a task from Human Review back to Planning stage when requirements change, instead of only looping through QA Fixer.

---

Problem

When a task reaches Human Review, there are only two options:

Action	Result
Approve	Move to Done
Request Changes	Send to QA Fixer (can only fix bugs, not change the plan)

What's missing? A way to update requirements and re-run the Planner Agent when the plan itself needs to change.

When This Becomes a Problem

• Requirements were incomplete or misunderstood
• New features need to be added that require new subtasks
• Implementation approach needs fundamental restructuring
• Stakeholder feedback requires scope changes

The QA Fixer can only work within the existing plan. When the plan itself is wrong or incomplete, it keeps looping trying to "fix" something that actually needs replanning.

Current Workaround

Users must discard the task, manually edit spec files, delete the implementation plan, and restart from scratch. This loses all progress and context.

---

Proposed Solution

Add "Replan" as Third Option

Human Review Actions:
┌──────────┐  ┌─────────────────┐  ┌──────────────┐
│ Approve  │  │ Request Changes │  │   Replan 🔄  │
└──────────┘  └─────────────────┘  └──────────────┘
     │                │                    │
     ↓                ↓                    ↓
   Done          QA Fixer            Planning
              (fix bugs)         (new requirements)

Workflow Change

Current:

Planning → In Progress → AI Review → Human Review → Done
                              ↑______________|
                                 QA Fixer

Proposed:

Planning → In Progress → AI Review → Human Review → Done
    ↑                         ↑______________|
    |                            QA Fixer
    |_____________________________________|
                   Replan

What Happens When "Replan" is Clicked

1. Dialog opens to edit requirements and explain why replanning is needed
2. User can choose to keep existing code or start fresh
3. Planner Agent re-runs with updated requirements + context about previous work
4. Task moves back to Planning column
5. Normal flow continues with new plan

---

Why This Matters

Current Approach	With Replan
Must discard and recreate task	One-click from Human Review
Loses all existing code	Option to preserve work
Loses implementation context	Planner knows what was done
Manual file editing required	Edit requirements in UI

---

Example Use Case

"I asked for user authentication. During review, I realized we also need OAuth and 2FA."

Today:

1. Discard task
2. Create new task with updated requirements
3. Start completely over

With Replan:

1. Click "Replan" in Human Review
2. Add OAuth and 2FA to requirements
3. Planner creates new subtasks that build on existing auth code
4. Continue with preserved context

---

Summary Table

Situation	Use This
Bug in code	Request Changes → QA Fixer
Missing edge case	Request Changes → QA Fixer
Need new feature	Replan → Planner
Wrong architecture	Replan → Planner
Requirements changed	Replan → Planner

The core idea: When the plan needs to change (not just the code), users should be able to go back to Planning without losing their work.

---

Labels: feature, workflow

[cloudconsultants]

This is definitely a Must! The Planning phase is the most critical aspect, since the LLM needs feedback after presenting a plan the current workflow forces you to first have the plan executed and only then you can ask for a "correction", this consumes tokes unnecessarily.

I am forced to fix the specs.md via an independent claude code session from terminal, but this way I violate all the structure of the Auto Code project.

[ariccb]

I agree with this fully! To add to this, I believe if you submit a "Request Changes", that it should immediately show up in the Subtasks where the agent then decides if this is a simple bug fix request or requiring feature planning modifications.

The issue right now is there's no visual feedback for what happened to your change request after you hit the button- it just disappears. The progress bar stays at 100%, and the only indicator that something is still working is going to the logs to see it moving again after scrolling ALL the way down.