Hugo Nijhuis
ae4e18feee
The vision system now guides defining WHO we build for and WHAT they're trying to achieve before jumping into goals and issues. Updated vision-management skill: - New vision.md structure with Personas and Jobs to Be Done sections - Guidance for defining good personas (specific, characterized, limited) - Guidance for jobs to be done (outcome-focused, in their voice, pain-aware) - Milestones now tied to personas and jobs with structured descriptions - Issue alignment checks persona/job fit before milestone fit Updated vision command: - Guides through persona and JTBD definition when creating vision - Output format shows personas and jobs prominently - Guidelines emphasize traceability to personas Updated plan-issues command: - Identifies persona and job before breaking down work - Plan presentation includes For/Job/Supports context - Flags misalignment with persona/job, not just goals 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
51 lines
1.8 KiB
Markdown
51 lines
1.8 KiB
Markdown
---
|
|
description: Plan and create issues for a feature or improvement. Breaks down work into well-structured issues with vision alignment.
|
|
argument-hint: <feature-description>
|
|
---
|
|
|
|
# Plan Feature: $1
|
|
|
|
@~/.claude/skills/gitea/SKILL.md
|
|
@~/.claude/skills/roadmap-planning/SKILL.md
|
|
@~/.claude/skills/issue-writing/SKILL.md
|
|
@~/.claude/skills/vision-management/SKILL.md
|
|
|
|
1. **Check vision context**: If `vision.md` exists, read it to understand personas, jobs to be done, and goals
|
|
2. **Identify persona**: Which persona does "$1" serve?
|
|
3. **Identify job**: Which job to be done does this enable?
|
|
4. **Understand the feature**: Analyze what "$1" involves
|
|
5. **Explore the codebase** if needed to understand context
|
|
6. **Break down** into discrete, actionable issues:
|
|
- Each issue should be independently completable
|
|
- Clear dependencies between issues
|
|
- Appropriate scope (not too big, not too small)
|
|
|
|
7. **Present the plan** (include vision alignment if vision exists):
|
|
```
|
|
## Proposed Issues for: $1
|
|
|
|
For: [Persona name]
|
|
Job: "[Job to be done this enables]"
|
|
Supports: [Milestone/Goal name]
|
|
|
|
1. [Title] - Brief description
|
|
Dependencies: none
|
|
|
|
2. [Title] - Brief description
|
|
Dependencies: #1
|
|
|
|
3. [Title] - Brief description
|
|
Dependencies: #1, #2
|
|
```
|
|
|
|
If the feature doesn't align with any persona/job/goal, note this and ask if:
|
|
- A new persona or job should be added to the vision
|
|
- A new milestone should be created
|
|
- This should be added as a non-goal
|
|
- Proceed anyway (with justification)
|
|
|
|
8. **Ask for approval** before creating issues
|
|
9. **Create issues** in dependency order (blockers first)
|
|
10. **Link dependencies** using `tea issues deps add <issue> <blocker>` for each dependency
|
|
11. **Present summary** with links to created issues and dependency graph
|