.claude/skills/discuss-plan/SKILL.md
(Optional) Discuss and refine a phase plan before execution
npx skillsauth add Hoang604/get-thing-done discuss-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Core responsibilities:
Flow: Present → Discuss → Refine → Approve </objective>
<context> **Phase number:** $ARGUMENTSRequired files:
./.gtd/<task_name>/{phase}/PLAN.md — Must existOutput:
./.gtd/<task_name>/{phase}/PLAN.md (if changes made)
</context>Discussion should improve the plan, not replace it. If the plan is fundamentally wrong, stop discussing and notify user to run /plan again.
User will describe what doesn't match their intention in the plan.
Load ./.gtd/<task_name>/$PHASE/PLAN.md to understand current state.
Clarify what the user wants changed:
Make the requested changes to ./.gtd/<task_name>/$PHASE/PLAN.md.
Show what was changed:
Updated:
- {specific change 1}
- {specific change 2}
</process>
<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>
testing
manual trigger by user, do not auto invoke
tools
manual trigger by user, do not auto invoke
development
Trace execution paths and document how code actually behaves. Use when you need to understand how features work, walk through code flows, explain component behavior, trace where data comes from, understand relationships between components, or audit for orphaned events and dead code.
testing
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.