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>

commands/plan-issues.md

@@ -10,39 +10,41 @@ argument-hint: <feature-description>
 @~/.claude/skills/issue-writing/SKILL.md
 @~/.claude/skills/vision-management/SKILL.md
 
-1. **Check vision context**: If `vision.md` exists, read it to understand current goals and focus
-2. **Understand the feature**: Analyze what "$1" involves
-3. **Explore the codebase** if needed to understand context
-4. **Break down** into discrete, actionable issues:
+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)
 
-5. **Present the plan** (include vision alignment if vision exists):
+7. **Present the plan** (include vision alignment if vision exists):
    ```
    ## Proposed Issues for: $1
 
-   Vision Alignment: Supports [Goal N: description]
+   For: [Persona name]
+   Job: "[Job to be done this enables]"
+   Supports: [Milestone/Goal name]
 
    1. [Title] - Brief description
       Dependencies: none
-      Supports: Goal N
 
    2. [Title] - Brief description
       Dependencies: #1
-      Supports: Goal N
 
    3. [Title] - Brief description
       Dependencies: #1, #2
-      Supports: Goal N
    ```
 
-   If the feature doesn't align with any vision goal, note this and ask if:
-   - The vision should be updated to include this as a goal
+   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)
 
-6. **Ask for approval** before creating issues
-7. **Create issues** in dependency order (blockers first)
-8. **Link dependencies** using `tea issues deps add <issue> <blocker>` for each dependency
-9. **Present summary** with links to created issues and dependency graph
+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

commands/vision.md

@@ -25,9 +25,15 @@ Issues are assigned to milestones. Progress is visible through milestone complet
 
 2. **If no vision exists**:
    - Ask the user if they want to create one
-   - Guide them through the philosophy: purpose, principles, non-goals
+   - Guide them through defining:
+     1. **Personas**: Who are we building for? (2-4 specific personas)
+     2. **Jobs to be done**: What are they trying to achieve?
+     3. **The problem**: What pain points exist today?
+     4. **The solution**: How does this product address their jobs?
+     5. **Guiding principles**: What beliefs guide decisions?
+     6. **Non-goals**: What are we explicitly NOT doing?
    - Create `vision.md` (do NOT include goals/progress - that's milestones)
-   - Ask about initial goals and create them as Gitea milestones
+   - Ask about initial goals tied to personas/jobs, create as Gitea milestones
 
 3. **If vision exists**:
    - Display the vision philosophy from `vision.md`
@@ -54,15 +60,25 @@ Issues are assigned to milestones. Progress is visible through milestone complet
 ## Output Format
 
 ```
+## Who We Serve
+
+- **[Persona 1]**: [Brief description]
+- **[Persona 2]**: [Brief description]
+
+## What They're Trying to Achieve
+
+- "[Job to be done 1]"
+- "[Job to be done 2]"
+
 ## Vision
 
-[Summary of vision.md purpose/principles]
+[Summary of problem/solution from vision.md]
 
 ## Goals (Milestones)
 
-| Goal | Progress | Due |
-|------|----------|-----|
-| [title] | 3/5 issues | [date] |
+| Goal | For | Progress | Due |
+|------|-----|----------|-----|
+| [title] | [Persona] | 3/5 issues | [date] |
 
 ## Current Focus
 
@@ -71,8 +87,10 @@ Issues are assigned to milestones. Progress is visible through milestone complet
 
 ## Guidelines
 
-- vision.md is the stable "why" document - update rarely
-- Milestones are the actionable goals - create/close as needed
+- vision.md is the stable "why" and "who" document - update rarely
+- Personas and jobs to be done are foundational - everything traces back to them
+- Milestones are actionable goals - each should serve a specific persona's job
 - Assign issues to milestones to track progress
-- Use milestone descriptions for success criteria
+- Use milestone descriptions for: persona, job, success criteria
 - Due dates on milestones are optional but help prioritization
+- If you can't tie work to a persona/job, question whether it should be done