Clarifies /vision is for product-level vision, distinct from /manifesto which handles organization-level vision. Changes: - Added architecture table showing org vs product vs goals levels - Process now checks for manifesto first for org context - Output format includes Organization Context section - Guidelines clarify when to use /manifesto vs /vision - Product personas/jobs extend (not duplicate) org-level ones Closes #41 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
3.5 KiB
3.5 KiB
description, argument-hint
| description | argument-hint | |
|---|---|---|
| View the product vision and goal progress. Manages vision.md and Gitea milestones. |
|
Product Vision
@/.claude/skills/vision-management/SKILL.md
@/.claude/skills/gitea/SKILL.md
This command manages product-level vision. For organization-level vision, use /manifesto.
Architecture
| Level | Document | Purpose | Command |
|---|---|---|---|
| Organization | manifesto.md |
Who we are, shared personas, beliefs | /manifesto |
| Product | vision.md |
Product-specific personas, jobs, solution | /vision |
| Goals | Gitea milestones | Measurable progress toward vision | /vision goals |
Product vision inherits from and extends the organization manifesto.
Process
-
Check for organization manifesto: Note if
manifesto.mdexists (provides org context) -
Check for product vision: Look for
vision.mdin the current repo root -
If no vision exists:
- Reference the organization manifesto if it exists
- Ask if the user wants to create a product vision
- Guide them through defining:
- Product personas: Who does this product serve? (may extend org personas)
- Product jobs: What specific jobs does this product address?
- The problem: What pain points does this product solve?
- The solution: How does this product address those jobs?
- Product principles: Any product-specific principles (beyond org principles)?
- Product non-goals: What is this product explicitly NOT doing?
- Create
vision.md - Ask about initial goals, create as Gitea milestones
-
If vision exists:
- Display organization context (if manifesto exists)
- Display the product vision from
vision.md - Show current milestones and their progress:
tea milestones - Check if
$1specifies 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 "For: <persona>
Job: Success: "
View issues in a milestone
tea milestones issues
Close a completed goal
tea milestones close
## Output Format
Organization Context
See manifesto for shared personas, beliefs, and principles. [Link or note about manifesto.md location]
Product: [Name]
Who This Product Serves
- [Persona 1]: [Product-specific description]
- [Persona 2]: [Product-specific description]
What They're Trying to Achieve
- "[Product-specific job 1]"
- "[Product-specific job 2]"
Product 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
- Product vision builds on organization manifesto - don't duplicate, extend
- Product personas can be more specific versions of org personas
- Product jobs should trace back to org-level jobs to be done
- Milestones are product-specific goals toward the vision
- Use `/manifesto` for organization-level identity and beliefs
- Use `/vision` for product-specific direction and goals
- If this is the architecture repo itself, use `/manifesto` instead