Add personas and jobs to be done to vision system
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>
This commit is contained in:
@@ -22,39 +22,81 @@ The vision system has two layers:
|
||||
|
||||
## Vision Document Structure
|
||||
|
||||
The vision.md file should contain the stable "why" - not progress tracking:
|
||||
The vision.md file should contain the stable "why" and "who" - not progress tracking:
|
||||
|
||||
```markdown
|
||||
# Vision
|
||||
|
||||
## Who We Serve (Personas)
|
||||
The people we're building for and what characterizes them.
|
||||
|
||||
- **Persona Name**: Brief description of who they are, their context, constraints
|
||||
|
||||
## What They're Trying to Achieve (Jobs to Be Done)
|
||||
The outcomes our personas are trying to accomplish - in their words.
|
||||
|
||||
- "Help me [achieve outcome] without [pain point]"
|
||||
- "Help me [do thing] so I can [benefit]"
|
||||
|
||||
## The Problem
|
||||
What problem does this product solve? Who benefits?
|
||||
Current pain points that prevent our personas from achieving their jobs.
|
||||
|
||||
## The Solution
|
||||
How does this product solve the problem?
|
||||
How this product addresses the jobs to be done.
|
||||
|
||||
## Guiding Principles
|
||||
Core beliefs that guide decisions.
|
||||
|
||||
## Non-Goals
|
||||
What we're explicitly NOT doing.
|
||||
What we're explicitly NOT doing (and why).
|
||||
```
|
||||
|
||||
Do NOT include goals, progress, or focus in vision.md - that's what milestones are for.
|
||||
|
||||
## Defining Personas
|
||||
|
||||
Good personas are:
|
||||
- **Specific**: Not "developers" but "solo developers shipping MVPs"
|
||||
- **Characterized**: Include constraints, context, priorities
|
||||
- **Limited**: 2-4 personas max, or you're building for everyone (no one)
|
||||
|
||||
| Bad | Good |
|
||||
|-----|------|
|
||||
| "Users" | "Solo developer shipping side projects on evenings/weekends" |
|
||||
| "Developers" | "Small team lead coordinating 2-5 engineers" |
|
||||
| "Companies" | "Early-stage startup with no dedicated DevOps" |
|
||||
|
||||
## Defining Jobs to Be Done
|
||||
|
||||
Jobs should be:
|
||||
- **Outcome-focused**: What they want to achieve, not what they do
|
||||
- **In their voice**: How they'd describe it, not technical jargon
|
||||
- **Pain-aware**: Include what's hard about it today
|
||||
|
||||
Format: "Help me [outcome] without [pain]" or "Help me [action] so I can [benefit]"
|
||||
|
||||
| Bad | Good |
|
||||
|-----|------|
|
||||
| "Git integration" | "Help me commit and push without remembering git commands" |
|
||||
| "Issue tracking" | "Help me know what to work on next without checking 5 tools" |
|
||||
| "Code review" | "Help me catch bugs before they ship without slowing down" |
|
||||
|
||||
## Creating a Vision
|
||||
|
||||
When no vision exists:
|
||||
|
||||
1. **Identify the problem**: What pain point does this solve?
|
||||
2. **Define the solution**: How does the product address it?
|
||||
3. **Set guiding principles**: What beliefs guide decisions?
|
||||
4. **Document non-goals**: What are you explicitly NOT doing?
|
||||
5. **Create initial milestones**: 3-5 measurable goals
|
||||
1. **Define personas**: Who are we building for? (2-4 specific personas)
|
||||
2. **Identify jobs to be done**: What are they trying to achieve?
|
||||
3. **Articulate the problem**: What pain points prevent them from achieving their jobs?
|
||||
4. **Define the solution**: How does the product address these jobs?
|
||||
5. **Set guiding principles**: What beliefs guide decisions?
|
||||
6. **Document non-goals**: What are you explicitly NOT doing?
|
||||
7. **Create initial milestones**: 3-5 measurable goals tied to personas/jobs
|
||||
|
||||
### Good Goals (Milestones)
|
||||
|
||||
- Specific and measurable
|
||||
- Tied to a persona and job to be done
|
||||
- Outcome-focused (not activity-focused)
|
||||
- Have clear success criteria in the description
|
||||
|
||||
@@ -64,6 +106,25 @@ When no vision exists:
|
||||
| "Better UX" | "User can complete checkout in under 60 seconds" |
|
||||
| "More features" | "Support 3 export formats (CSV, JSON, PDF)" |
|
||||
|
||||
### Tying Milestones to Personas
|
||||
|
||||
Each milestone should clearly serve a persona's job to be done:
|
||||
|
||||
```
|
||||
Milestone: "Automate routine git workflows"
|
||||
For: Solo developer
|
||||
Job: "Help me commit and push without remembering git commands"
|
||||
Success: /commit, /pr commands handle 80% of git workflows
|
||||
```
|
||||
|
||||
Include persona context in milestone descriptions:
|
||||
```bash
|
||||
tea milestones create --title "Automate routine git workflows" \
|
||||
--description "For: Solo developer
|
||||
Job: Ship without context switching to git commands
|
||||
Success: /commit and /pr commands handle 80% of workflows"
|
||||
```
|
||||
|
||||
## Managing Goals with Milestones
|
||||
|
||||
```bash
|
||||
@@ -98,18 +159,24 @@ Progress is automatically tracked through open/closed issue counts.
|
||||
|
||||
When creating or reviewing issues:
|
||||
|
||||
1. **Check goal alignment**: Does this issue support a milestone?
|
||||
2. **Assign to milestone**: Link the issue to the relevant goal
|
||||
3. **Prioritize by focus**: Issues in priority milestones get worked first
|
||||
4. **Flag misalignment**: Issues without a milestone need justification
|
||||
1. **Check persona alignment**: Which persona does this serve?
|
||||
2. **Check job alignment**: Which job to be done does this enable?
|
||||
3. **Check goal alignment**: Does this issue support a milestone?
|
||||
4. **Assign to milestone**: Link the issue to the relevant goal
|
||||
5. **Prioritize by focus**: Issues in priority milestones get worked first
|
||||
6. **Flag misalignment**: Issues without clear persona/milestone need justification
|
||||
|
||||
Every issue should trace back to: "This helps [persona] achieve [job] by [outcome]."
|
||||
|
||||
### Identifying Gaps
|
||||
|
||||
Compare milestones to current backlog:
|
||||
Compare vision to current work:
|
||||
|
||||
- Which milestones have no issues?
|
||||
- Which milestones have stalled (no recent progress)?
|
||||
- Are there issues without a milestone?
|
||||
- **Underserved personas**: Which personas have few milestones/issues?
|
||||
- **Unaddressed jobs**: Which jobs to be done have no work toward them?
|
||||
- **Empty milestones**: Which milestones have no issues?
|
||||
- **Stalled milestones**: Which milestones have no recent progress?
|
||||
- **Orphan issues**: Are there issues without a milestone?
|
||||
|
||||
## Connecting Retros to Vision
|
||||
|
||||
|
||||
Reference in New Issue
Block a user