discuss-plan

Review and refine a phase plan in PLAN.md before execution.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Hoang604/get-thing-done --skill discuss-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discuss-plan
Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/discuss-plan
Command: npx skills add https://github.com/Hoang604/get-thing-done --skill discuss-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The discuss-plan skill helps teams review and refine a phase plan before execution, preventing misalignment and wasted effort.

Core Features & Use Cases

  • Present the plan clearly to stakeholders
  • Answer questions about approach and constraints
  • Incorporate feedback and update the plan in place
  • Require explicit approval before proceeding to the next phase

Quick Start

Review the current phase plan at ./.gtd/<task_name>/{phase}/PLAN.md and propose refinements.

Frequently Asked Questions about discuss-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review and refine a phase plan before execution?

To refine a phase plan before execution, you review the PLAN.md file and propose updates through a structured flow. This process presents the plan, discusses feedback, refines details, and requires explicit approval before proceeding.

What is the best way to incorporate feedback into a GTD plan review?

The best way to incorporate GTD feedback is to discuss proposed changes and persist them directly to the PLAN.md file. This preserves an auditable trail of iterative improvements within your workflow.

How does plan approval work within a GTD workflow?

Plan approval in a GTD workflow requires explicit confirmation before proceeding to the next phase. The flow moves through Present, Discuss, Refine, and Approve stages to prevent misalignment and wasted effort.

Do I need a specific file structure to discuss phase plan updates?

Yes, you need a PLAN.md file located at ./.gtd/<task_name>/{phase}/PLAN.md. The skill reads this specific file path to present the current phase plan and apply refinements.

Why require explicit approval before moving to the next execution phase?

Explicit approval prevents misalignment and wasted effort by ensuring stakeholders agree on the refined plan. Changes are persisted to PLAN.md only after completing the discuss and refine stages.