During vision/milestone/issue planning for Arcadia, we jumped from milestones directly to issues without understanding user workflows first.
Problem / Observation
The /plan-issues skill goes straight from 'understand the feature' to 'break down the work' without a formal discovery phase. This led to proposing issues 'out of thin air' that had to be reworked.
Suggested Improvement
Add a discovery step between understanding the feature and breaking down work:
### Discovery Phase (before creating issues)
For each milestone/feature, answer:
1.**Who** is the user?
2.**What's their goal?**3.**What's the workflow** (step by step)?
4.**What exists** today?
5.**What's the MVP** to deliver value?
Then derive issues from workflow gaps, not from guessing.
Affected Files
skills/roadmap-planning/SKILL.md
Or create new skills/milestone-discovery/SKILL.md
## Context
During vision/milestone/issue planning for Arcadia, we jumped from milestones directly to issues without understanding user workflows first.
## Problem / Observation
The /plan-issues skill goes straight from 'understand the feature' to 'break down the work' without a formal discovery phase. This led to proposing issues 'out of thin air' that had to be reworked.
## Suggested Improvement
Add a discovery step between understanding the feature and breaking down work:
```markdown
### Discovery Phase (before creating issues)
For each milestone/feature, answer:
1. **Who** is the user?
2. **What's their goal?**
3. **What's the workflow** (step by step)?
4. **What exists** today?
5. **What's the MVP** to deliver value?
Then derive issues from workflow gaps, not from guessing.
```
## Affected Files
- skills/roadmap-planning/SKILL.md
- Or create new skills/milestone-discovery/SKILL.md
HugoNijhuis
added this to the Continuous improvement loop milestone 2026-01-04 11:57:40 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
During vision/milestone/issue planning for Arcadia, we jumped from milestones directly to issues without understanding user workflows first.
Problem / Observation
The /plan-issues skill goes straight from 'understand the feature' to 'break down the work' without a formal discovery phase. This led to proposing issues 'out of thin air' that had to be reworked.
Suggested Improvement
Add a discovery step between understanding the feature and breaking down work:
Affected Files