#48 pm skill: planning feedback iterations must use resume=true

[Anonymous]

Originally created by: kumaakh

Context

During planning phase refinement, when user or reviewer provides feedback on a generated plan, the PM skill must use resume=true when dispatching the next execute_prompt call to the planning member.

Rule

Planning feedback iterations MUST use resume=true

When user or reviewer feedback is provided on an existing plan, those iterations depend on the context created by the previous planning session. Using resume=false causes the member to lose this context and re-interpret requirements from scratch, leading to:

• Merged phases being restructured incorrectly
• Loss of original phase boundaries
• Confusion about verified checkpoints
• Wasted token budget re-thinking the same decisions

Application

• Initial plan generation: execute_prompt(..., resume=false) ✓
• User feedback: "Club phases 1+2, clarify phase 3" → next dispatch: execute_prompt(..., resume=true) ✓
• Reviewer feedback: "Expand task descriptions" → next dispatch: execute_prompt(..., resume=true) ✓
• User says "start over": Only then use execute_prompt(..., resume=false) ✓

References

Memory file: feedback_pm_resume_rule.md — documents the complete rule with why and how-to-apply

Related

• PM skill documentation: /pm plan, /pm pair, /pm start
• Session context: Planning feedback is given based on past context, not a blank slate

[Anonymous]

Ticket changed by: kumaakh

• status: open --> closed