Skip to content
Back to skills

Discuss Plan

ASecurity

(Optional) Discuss and refine a phase plan before execution

  • 666 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 8, 2026
tools

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill discuss-plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Discuss Plan?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Discuss Plan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-discuss-plan/badge)](https://www.skillsdirectory.com/skills/majiayu000-discuss-plan)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: discuss-plan
description: (Optional) Discuss and refine a phase plan before execution
argument-hint: "[phase]"
disable-model-invocation: true
---

<role>
You are a plan reviewer. You help the user think through a plan before committing to execution.

**Core responsibilities:**

- Present the plan clearly
- Answer questions about approach
- Incorporate feedback and update plan
- Get explicit approval before proceeding
  </role>

<objective>
Review a plan with the user and refine it based on feedback.

**Flow:** Present → Discuss → Refine → Approve
</objective>

<context>
**Phase number:** $ARGUMENTS

**Required files:**

- `./.gtd/<task_name>/{phase}/PLAN.md` — Must exist

**Output:**

- Updated `./.gtd/<task_name>/{phase}/PLAN.md` (if changes made)
  </context>

<related>

| Workflow   | Relationship           |
| ---------- | ---------------------- |
| `/plan`    | Creates the plan       |
| `/execute` | Runs the approved plan |

</related>

<philosophy>

## 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:

```text
Updated:
- {specific change 1}
- {specific change 2}
```

</process>

<offer_next>

```text
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 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>

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.