Your mission
Interview the user with critical questions to validate assumptions, confirm decisions, and surface potential issues in an implementation plan before coding begins.
Plan Resolution
- If
$ARGUMENTS provided -> Use that path
- Else check
## Plan Context section -> Use active plan path
- If no plan found -> Ask user to specify path or run
/plan-deep first
Configuration (from injected context)
Check ## Plan Context section for validation settings:
mode - Controls auto/prompt/off behaviorquestions - Range like 3-8 (min-max)
These values are automatically injected from user config. Use them as constraints.
Workflow
Step 1: Read Plan Files
Read the plan directory:
plan.md - Overview and phases listphase-*.md - All phase files- Look for decision points, assumptions, risks, tradeoffs
Step 2: Extract Question Topics
Scan plan content for:
| Category |
Keywords to detect |
| Architecture |
"approach", "pattern", "design", "structure", "database", "API" |
| Assumptions |
"assume", "expect", "should", "will", "must", "default" |
| Tradeoffs |
"tradeoff", "vs", "alternative", "option", "choice", "either/or" |
| Risks |
"risk", "might", "could fail", "dependency", "blocker", "concern" |
| Scope |
"phase", "MVP", "future", "out of scope", "nice to have" |
Step 3: Generate Questions
For each detected topic, formulate a concrete question:
Question format rules:
- Each question must have 2-4 concrete options
- Mark recommended option with "(Recommended)" suffix
- Include "Other" option is automatic - don't add it
- Questions should surface implicit decisions
Example questions:
Category: Architecture
Question: "How should the validation results be persisted?"
Options:
1. Save to plan.md frontmatter (Recommended) - Updates existing plan
2. Create validation-answers.md - Separate file for answers
3. Don't persist - Ephemeral validation only
Category: Assumptions
Question: "The plan assumes API rate limiting is not needed. Is this correct?"
Options:
1. Yes, rate limiting not needed for MVP
2. No, add basic rate limiting now (Recommended)
3. Defer to Phase 2
Step 4: Interview User
Use AskUserQuestion tool to present questions.
Rules:
- Use question count from
## Plan Context -> Validation: mode=X, questions=MIN-MAX
- Group related questions when possible (max 4 questions per tool call)
- Focus on: assumptions, risks, tradeoffs, architecture
Step 5: Document Answers
After collecting answers, update the plan:
- Add
## Validation Summary section to plan.md:
## Validation Summary
**Validated:** {date}
**Questions asked:** {count}
### Confirmed Decisions
- {decision 1}: {user choice}
- {decision 2}: {user choice}
### Action Items
- [ ] {any changes needed based on answers}
- If answers require plan changes, note them but do not modify phase files - just document what needs updating.
Output
After validation completes, provide summary:
- Number of questions asked
- Key decisions confirmed
- Any items flagged for plan revision
- Recommendation: proceed to implementation or revise plan first
Important Notes
IMPORTANT: Only ask questions about genuine decision points - don't manufacture artificial choices.
IMPORTANT: If plan is simple with few decisions, it's okay to ask fewer than min questions.
IMPORTANT: Prioritize questions that could change implementation significantly.
1---2name: plan-validate-33description: (ePost) Validate plan with critical questions interview4---5
6## Your mission
7
8Interview the user with critical questions to validate assumptions, confirm decisions, and surface potential issues in an implementation plan before coding begins.
9
10## Plan Resolution
11
121. If `$ARGUMENTS` provided -> Use that path
132. Else check `## Plan Context` section -> Use active plan path
143. If no plan found -> Ask user to specify path or run `/plan-deep` first
15
16## Configuration (from injected context)
17
18Check `## Plan Context` section for validation settings:
19- `mode` - Controls auto/prompt/off behavior
20- `questions` - Range like `3-8` (min-max)
21
22These values are automatically injected from user config. Use them as constraints.
23
24## Workflow
25
26### Step 1: Read Plan Files
27
28Read the plan directory:
29- `plan.md` - Overview and phases list
30- `phase-*.md` - All phase files
31- Look for decision points, assumptions, risks, tradeoffs
32
33### Step 2: Extract Question Topics
34
35Scan plan content for:
36
37| Category | Keywords to detect |
38|----------|-------------------|
39| **Architecture** | "approach", "pattern", "design", "structure", "database", "API" |
40| **Assumptions** | "assume", "expect", "should", "will", "must", "default" |
41| **Tradeoffs** | "tradeoff", "vs", "alternative", "option", "choice", "either/or" |
42| **Risks** | "risk", "might", "could fail", "dependency", "blocker", "concern" |
43| **Scope** | "phase", "MVP", "future", "out of scope", "nice to have" |
44
45### Step 3: Generate Questions
46
47For each detected topic, formulate a concrete question:
48
49**Question format rules:**
50- Each question must have 2-4 concrete options
51- Mark recommended option with "(Recommended)" suffix
52- Include "Other" option is automatic - don't add it
53- Questions should surface implicit decisions
54
55**Example questions:**
56
57```
58Category: Architecture
59Question: "How should the validation results be persisted?"
60Options:
611. Save to plan.md frontmatter (Recommended) - Updates existing plan
622. Create validation-answers.md - Separate file for answers
633. Don't persist - Ephemeral validation only
64```
65
66```
67Category: Assumptions
68Question: "The plan assumes API rate limiting is not needed. Is this correct?"
69Options:
701. Yes, rate limiting not needed for MVP
712. No, add basic rate limiting now (Recommended)
723. Defer to Phase 2
73```
74
75### Step 4: Interview User
76
77Use `AskUserQuestion` tool to present questions.
78
79**Rules:**
80- Use question count from `## Plan Context` -> `Validation: mode=X, questions=MIN-MAX`
81- Group related questions when possible (max 4 questions per tool call)
82- Focus on: assumptions, risks, tradeoffs, architecture
83
84### Step 5: Document Answers
85
86After collecting answers, update the plan:
87
881. Add `## Validation Summary` section to `plan.md`:
89```markdown
90## Validation Summary
91
92**Validated:** {date}
93**Questions asked:** {count}
94
95### Confirmed Decisions
96- {decision 1}: {user choice}
97- {decision 2}: {user choice}
98
99### Action Items
100- [ ] {any changes needed based on answers}
101```
102
1032. If answers require plan changes, note them but **do not modify phase files** - just document what needs updating.
104
105## Output
106
107After validation completes, provide summary:
108- Number of questions asked
109- Key decisions confirmed
110- Any items flagged for plan revision
111- Recommendation: proceed to implementation or revise plan first
112
113## Important Notes
114
115**IMPORTANT:** Only ask questions about genuine decision points - don't manufacture artificial choices.
116**IMPORTANT:** If plan is simple with few decisions, it's okay to ask fewer than min questions.
117**IMPORTANT:** Prioritize questions that could change implementation significantly.
majiayu000