Files

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>

2026-01-07 17:52:17 +01:00

2.9 KiB

Raw Blame History

description, argument-hint

description

argument-hint

View the product vision and goal progress. Manages vision.md and Gitea milestones.

goals

Product Vision

@~~/.claude/skills/vision-management/SKILL.md @~~/.claude/skills/gitea/SKILL.md

Architecture

The vision system has two layers:

Layer	Purpose	Location
vision.md	North star philosophy (why, principles, non-goals)	File in repo root
Milestones	Goals with progress tracking	Gitea milestones

Issues are assigned to milestones. Progress is visible through milestone completion.

Process

Check for existing vision: Look for vision.md in the current repo root.
If no vision exists:
- Ask the user if they want to create one
- 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 tied to personas/jobs, create as Gitea milestones
If vision exists:
- Display the vision philosophy from vision.md
- Show current milestones and their progress: tea milestones
- Check if $1 specifies an action:
  - goals: Manage milestones (add, close, view progress)
- If no action specified, just display the current state

Managing Goals (milestones):

# List milestones with progress
tea milestones

# Create a new goal
tea milestones create --title "<goal>" --description "<success criteria>"

# View issues in a milestone
tea milestones issues <milestone-name>

# Close a completed goal
tea milestones close <milestone-name>

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 problem/solution from vision.md]

## Goals (Milestones)

| Goal | For | Progress | Due |
|------|-----|----------|-----|
| [title] | [Persona] | 3/5 issues | [date] |

## Current Focus

[Open milestones with nearest due dates or most activity]

Guidelines

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: 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

2.9 KiB Raw Blame History