Multi-session workflow for planning, validating, and implementing features.
- Session 1: Local plan file (
~/.claude/plans/) - Sessions 2+: GitHub issue
Once the plan is published to GitHub, the issue becomes the single source of truth. Avoid entering plan mode in subsequent sessions — this creates duplicate local files that diverge from the issue.
Design the implementation and publish the plan.
- Enter plan mode to explore the codebase and design the approach
- Claude writes the plan to
~/.claude/plans/ /plan-create— publishes the plan to a new GitHub issue- Keep the session open; validation resumes in a new session for fresh perspective
Issue structure:
- Description: Plan (living document, updated via
/plan-update) - Comments: Handoffs documenting implementation progress
Review the plan with fresh context. A new session helps identify gaps and assumptions that were invisible during planning.
/plan-resume <issue>— loads the plan from GitHub/plan-validate— checks clarity, accuracy, and completeness against the codebase/plan-update— pushes any revisions back to the issue (if needed)- Continue to implementation, or close and resume later
Execute the plan and document the work.
/plan-resume <issue>— skip if continuing from session 2- Implement the plan
/plan-handoff— documents what was done as an issue comment/pr-create— creates a pull request
Respond to PR feedback after review.
/plan-resume <issue>— loads context from the plan- Read the PR description (manual) — recall scope and decisions
- Fetch the review comments including inline feedback
- List issues to address from the review (manual)
- Implement fixes
/pr-response— posts a summary of changes made in response to review
For complex features spanning multiple sessions:
- End each session with
/plan-handoffto document progress - Start the next session with
/plan-resumeto load full context - Handoff comments accumulate chronologically, preserving session history
See .claude/rules/commands.md for the full command reference.