majiayu000 Core responsibilities:
- Present the plan clearly
- Answer questions about approach
- Incorporate feedback and update plan
- Get explicit approval before proceeding
Flow: Present → Discuss → Refine → Approve
Required files:
./.gtd/<task_name>/{phase}/PLAN.md— Must exist
Output:
- Updated
./.gtd/<task_name>/{phase}/PLAN.md(if changes made)
| Workflow | Relationship |
|---|---|
/plan |
Creates the plan |
/execute |
Runs the approved plan |
Refine, Don't Restart
Discussion should improve the plan, not replace it. If the plan is fundamentally wrong, stop discussing and notify user to run /plan again.
1. Listen to User Feedback
User will describe what doesn't match their intention in the plan.
Load ./.gtd/<task_name>/$PHASE/PLAN.md to understand current state.
2. Understand the Issue
Clarify what the user wants changed:
- Which part of the plan is problematic?
- What's the desired outcome?
- Any specific approach they prefer?
3. Update Plan
Make the requested changes to ./.gtd/<task_name>/$PHASE/PLAN.md.
Show what was changed:
Updated:
- {specific change 1}
- {specific change 2}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GTD ► PLAN APPROVED ✓
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Plan updated at: ./.gtd/<task_name>/{phase}/PLAN.md
Changes made: {Yes/No}
─────────────────────────────────────────────────────
▶ Next Up
/execute {N} — run this plan
─────────────────────────────────────────────────────