Update /vision command for product-level only

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>

commands/manifesto.md

@@ -0,0 +1,71 @@
+---
+description: View and manage the organization manifesto. Shows identity, personas, beliefs, and principles.
+---
+
+# Organization Manifesto
+
+@~/.claude/skills/vision-management/SKILL.md
+
+The manifesto defines the organization-level vision: who we are, who we serve, what we believe, and how we work. It is distinct from product-level vision (see `/vision`).
+
+## Process
+
+1. **Check for manifesto**: Look for `manifesto.md` in the current repo root.
+
+2. **If no manifesto exists**:
+   - Ask if the user wants to create one
+   - Guide through defining:
+     1. **Who We Are**: Organization identity
+     2. **Who We Serve**: 2-4 specific personas with context and constraints
+     3. **What They're Trying to Achieve**: Jobs to be done in their voice
+     4. **What We Believe**: Core beliefs including stance on AI-augmented development
+     5. **Guiding Principles**: Decision-making rules
+     6. **Non-Goals**: What we explicitly don't do
+   - Create `manifesto.md`
+
+3. **If manifesto exists**:
+   - Display formatted summary of the manifesto
+
+## Output Format
+
+When displaying an existing manifesto:
+
+```
+## Who We Are
+
+[Identity summary from manifesto]
+
+## Who We Serve
+
+- **[Persona 1]**: [Brief description]
+- **[Persona 2]**: [Brief description]
+- **[Persona 3]**: [Brief description]
+
+## What They're Trying to Achieve
+
+- "[Job to be done 1]"
+- "[Job to be done 2]"
+- "[Job to be done 3]"
+
+## What We Believe
+
+[Summary of key beliefs - especially AI-augmented development stance]
+
+## Guiding Principles
+
+1. [Principle 1]
+2. [Principle 2]
+3. [Principle 3]
+
+## Non-Goals
+
+- [Non-goal 1]
+- [Non-goal 2]
+```
+
+## Guidelines
+
+- The manifesto is the **organization-level** document - it applies across all products
+- Update rarely - this is foundational identity, not tactical direction
+- Product repos reference the manifesto but have their own `vision.md`
+- Use `/vision` for product-level vision management

commands/vision.md

@@ -8,47 +8,54 @@ argument-hint: [goals]
 @~/.claude/skills/vision-management/SKILL.md
 @~/.claude/skills/gitea/SKILL.md
 
+This command manages **product-level** vision. For organization-level vision, use `/manifesto`.
+
 ## 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
 
-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:
-     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`
    - Check if `$1` specifies an action:
      - `goals`: Manage milestones (add, close, view progress)
    - If no action specified, just display the current state
 
-4. **Managing Goals (milestones)**:
+5. **Managing Goals (milestones)**:
    ```bash
    # List milestones with progress
    tea milestones
 
    # 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
    tea milestones issues <milestone-name>
@@ -60,37 +67,44 @@ Issues are assigned to milestones. Progress is visible through milestone complet
 ## 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]
 
-## Goals (Milestones)
+### Goals (Milestones)
 
 | Goal | For | Progress | Due |
 |------|-----|----------|-----|
 | [title] | [Persona] | 3/5 issues | [date] |
 
-## Current Focus
+### Current Focus
 
 [Open milestones with nearest due dates or most activity]
 ```
 
 ## 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