flowmade-one/architecture
3
0
Fork 0
Code Issues 15 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Update /vision command for product-level only

Browse Source 
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>
This commit was merged in pull request #48.
This commit is contained in:
Hugo Nijhuis
2026-01-07 20:24:28 +01:00
parent a8a35575b5
commit c0ef16035c
1 changed files with 52 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

90
commands/vision.md
View File

@@ -8,47 +8,54 @@ argument-hint: [goals]
@~/.claude/skills/vision-management/SKILL.md @~/.claude/skills/vision-management/SKILL.md
@~/.claude/skills/gitea/SKILL.md @~/.claude/skills/gitea/SKILL.md
This command manages **product-level** vision. For organization-level vision, use `/manifesto`.
## Architecture ## Architecture
The vision system has two layers: | 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` |
| Layer | Purpose | Location | Product vision inherits from and extends the organization manifesto.
|-------|---------|----------|
| **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 ## Process
1. **Check for existing vision**: Look for `vision.md` in the current repo root. 1. **Check for organization manifesto**: Note if `manifesto.md` exists (provides org context)
2. **If no vision exists**: 2. **Check for product vision**: Look for `vision.md` in the current repo root
- Ask the user if they want to create one
3. **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: - Guide them through defining:
1. **Personas**: Who are we building for? (2-4 specific personas) 1. **Product personas**: Who does this product serve? (may extend org personas)
2. **Jobs to be done**: What are they trying to achieve? 2. **Product jobs**: What specific jobs does this product address?
3. **The problem**: What pain points exist today? 3. **The problem**: What pain points does this product solve?
4. **The solution**: How does this product address their jobs? 4. **The solution**: How does this product address those jobs?
5. **Guiding principles**: What beliefs guide decisions? 5. **Product principles**: Any product-specific principles (beyond org principles)?
6. **Non-goals**: What are we explicitly NOT doing? 6. **Product non-goals**: What is this product explicitly NOT doing?
- Create `vision.md` (do NOT include goals/progress - that's milestones) - Create `vision.md`
- Ask about initial goals tied to personas/jobs, create as Gitea milestones - Ask about initial goals, create as Gitea milestones
3. **If vision exists**: 4. **If vision exists**:
- Display the vision philosophy from `vision.md` - Display organization context (if manifesto exists)
- Display the product vision from `vision.md`
- Show current milestones and their progress: `tea milestones` - Show current milestones and their progress: `tea milestones`
- Check if `$1` specifies an action: - Check if `$1` specifies an action:
- `goals`: Manage milestones (add, close, view progress) - `goals`: Manage milestones (add, close, view progress)
- If no action specified, just display the current state - If no action specified, just display the current state
4. **Managing Goals (milestones)**: 5. **Managing Goals (milestones)**:
```bash ```bash
# List milestones with progress # List milestones with progress
tea milestones tea milestones
# Create a new goal # Create a new goal
tea milestones create --title "<goal>" --description "<success criteria>" tea milestones create --title "<goal>" --description "For: <persona>
Job: <job to be done>
Success: <criteria>"
# View issues in a milestone # View issues in a milestone
tea milestones issues <milestone-name> tea milestones issues <milestone-name>
@@ -60,37 +67,44 @@ Issues are assigned to milestones. Progress is visible through milestone complet
## Output Format ## Output Format
``` ```
## Who We Serve ## Organization Context
- **[Persona 1]**: [Brief description] See manifesto for shared personas, beliefs, and principles.
- **[Persona 2]**: [Brief description] [Link or note about manifesto.md location]
## What They're Trying to Achieve ## Product: [Name]
- "[Job to be done 1]" ### Who This Product Serves
- "[Job to be done 2]"
## Vision - **[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] [Summary of problem/solution from vision.md]
## Goals (Milestones) ### Goals (Milestones)
| Goal | For | Progress | Due | | Goal | For | Progress | Due |
|------|-----|----------|-----| |------|-----|----------|-----|
| [title] | [Persona] | 3/5 issues | [date] | | [title] | [Persona] | 3/5 issues | [date] |
## Current Focus ### Current Focus
[Open milestones with nearest due dates or most activity] [Open milestones with nearest due dates or most activity]
``` ```
## Guidelines ## Guidelines
- vision.md is the stable "why" and "who" document - update rarely - Product vision builds on organization manifesto - don't duplicate, extend
- Personas and jobs to be done are foundational - everything traces back to them - Product personas can be more specific versions of org personas
- Milestones are actionable goals - each should serve a specific persona's job - Product jobs should trace back to org-level jobs to be done
- Assign issues to milestones to track progress - Milestones are product-specific goals toward the vision
- Use milestone descriptions for: persona, job, success criteria - Use `/manifesto` for organization-level identity and beliefs
- Due dates on milestones are optional but help prioritization - Use `/vision` for product-specific direction and goals
- If you can't tie work to a persona/job, question whether it should be done - If this is the architecture repo itself, use `/manifesto` instead