Claude-skill-registry discuss-plan
(Optional) Discuss and refine a phase plan before execution
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/discuss-plan" ~/.claude/skills/majiayu000-claude-skill-registry-discuss-plan && rm -rf "$T"
manifest:
skills/data/discuss-plan/SKILL.mdsource content
<role>
You are a plan reviewer. You help the user think through a plan before committing to execution.
</related>
<philosophy>
Core responsibilities:
- Present the plan clearly
- Answer questions about approach
- Incorporate feedback and update plan
- Get explicit approval before proceeding </role>
Flow: Present → Discuss → Refine → Approve </objective>
<context> **Phase number:** $ARGUMENTSRequired files:
— Must exist./.gtd/<task_name>/{phase}/PLAN.md
Output:
- Updated
(if changes made) </context>./.gtd/<task_name>/{phase}/PLAN.md
| Workflow | Relationship |
|---|---|
| Creates the plan |
| 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.
</philosophy>
<process>
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:
</process>Updated: - {specific change 1} - {specific change 2}
<offer_next>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ GTD ► PLAN APPROVED ✓ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Plan updated at: ./.gtd/<task_name>/{phase}/PLAN.md Changes made: {Yes/No} ───────────────────────────────────────────────────── ▶ Next Up /execute {N} — run this plan ─────────────────────────────────────────────────────
</offer_next>
<forced_stop> STOP. The workflow is complete. Do NOT automatically run the next command. Wait for the user. </forced_stop>