During Arcadia issue planning, initial proposals were horizontal/technical slices (ADL syntax, then runtime, then UI) instead of vertical user-value slices.
Problem / Observation
The roadmap-planning and issue-writing skills don't explicitly guide toward vertical slices. This leads to issues like 'Add query syntax to ADL' instead of 'Domain expert can list all orders'.
Suggested Improvement
Add explicit guidance:
## Vertical vs Horizontal Slices
**Prefer vertical slices** - each issue delivers user-visible value:
- Good: 'User can save and reload their diagram'
- Bad: 'Add persistence layer' + 'Add save API' + 'Add load API'
**Test**: Can a user demo/test this issue independently?
- If yes → good vertical slice
- If no → probably a horizontal slice, break differently
**Break down by user capability, not technical layer.**
Affected Files
skills/roadmap-planning/SKILL.md
skills/issue-writing/SKILL.md
## Context
During Arcadia issue planning, initial proposals were horizontal/technical slices (ADL syntax, then runtime, then UI) instead of vertical user-value slices.
## Problem / Observation
The roadmap-planning and issue-writing skills don't explicitly guide toward vertical slices. This leads to issues like 'Add query syntax to ADL' instead of 'Domain expert can list all orders'.
## Suggested Improvement
Add explicit guidance:
```markdown
## Vertical vs Horizontal Slices
**Prefer vertical slices** - each issue delivers user-visible value:
- Good: 'User can save and reload their diagram'
- Bad: 'Add persistence layer' + 'Add save API' + 'Add load API'
**Test**: Can a user demo/test this issue independently?
- If yes → good vertical slice
- If no → probably a horizontal slice, break differently
**Break down by user capability, not technical layer.**
```
## Affected Files
- skills/roadmap-planning/SKILL.md
- skills/issue-writing/SKILL.md
HugoNijhuis
added this to the Ensure consistent quality milestone 2026-01-04 11:57:41 +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 Arcadia issue planning, initial proposals were horizontal/technical slices (ADL syntax, then runtime, then UI) instead of vertical user-value slices.
Problem / Observation
The roadmap-planning and issue-writing skills don't explicitly guide toward vertical slices. This leads to issues like 'Add query syntax to ADL' instead of 'Domain expert can list all orders'.
Suggested Improvement
Add explicit guidance:
Affected Files