Update vision system to properly extend manifesto

- Rebuild vision.md to trace personas, jobs, and principles back to manifesto
- Improve /vision command with inheritance guidance and templates
- Update vision-management skill with explicit inheritance rules and formats

Product visions now explicitly extend (not duplicate) organization manifesto.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

commands/vision.md

@@ -18,30 +18,56 @@ This command manages **product-level** vision. For organization-level vision, us
 | **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.
+Product vision **inherits from and extends** the organization manifesto - it should never duplicate.
 
 ## Process
 
-1. **Check for organization manifesto**: Note if `manifesto.md` exists (provides org context)
+1. **Load organization context**: Read `manifesto.md` from the architecture repo (`~/.claude/manifesto.md` or repo root)
+   - Extract personas (Who We Serve)
+   - Extract jobs to be done (What They're Trying to Achieve)
+   - Extract guiding principles
+   - Extract non-goals
 
 2. **Check for product vision**: Look for `vision.md` in the current repo root
 
 3. **If no vision exists**:
-   - Reference the organization manifesto if it exists
+   - Show the organization manifesto summary
    - Ask if the user wants to create a product vision
-   - Guide them through defining:
-     1. **Product personas**: Who does this product serve? (may extend org personas)
-     2. **Product jobs**: What specific jobs does this product address?
-     3. **The problem**: What pain points does this product solve?
-     4. **The solution**: How does this product address those jobs?
-     5. **Product principles**: Any product-specific principles (beyond org principles)?
-     6. **Product non-goals**: What is this product explicitly NOT doing?
-   - Create `vision.md`
+   - Guide them through defining (with inheritance):
+
+     **Who This Product Serves**
+     - Show manifesto personas first
+     - Ask: "Which personas does this product serve? How does it extend or specialize them?"
+     - Product personas should reference org personas with product-specific context
+
+     **What They're Trying to Achieve**
+     - Show manifesto jobs first
+     - Ask: "What product-specific jobs does this enable? How do they trace back to org jobs?"
+     - Use a table format showing the connection
+
+     **The Problem**
+     - What pain points does this product solve?
+
+     **The Solution**
+     - How does this product address those jobs?
+
+     **Product Principles**
+     - Show manifesto principles first
+     - Ask: "Any product-specific principles? These should extend, not duplicate."
+     - Each principle should note what org principle it extends
+
+     **Product Non-Goals**
+     - Show manifesto non-goals first
+     - Ask: "Any product-specific non-goals?"
+     - Org non-goals apply automatically
+
+   - Create `vision.md` with proper inheritance markers
    - Ask about initial goals, create as Gitea milestones
 
 4. **If vision exists**:
-   - Display organization context (if manifesto exists)
+   - Display organization context summary
    - Display the product vision from `vision.md`
+   - Validate inheritance (warn if vision duplicates rather than extends)
    - Show current milestones and their progress: `tea milestones`
    - Check if `$1` specifies an action:
      - `goals`: Manage milestones (add, close, view progress)
@@ -64,47 +90,101 @@ Success: <criteria>"
    tea milestones close <milestone-name>
    ```
 
+## Vision Structure Template
+
+```markdown
+# Vision
+
+This product vision builds on the [organization manifesto](link-to-manifesto).
+
+## Who This Product Serves
+
+### [Persona Name]
+
+[Product-specific description]
+
+*Extends: [Org persona] (from manifesto)*
+
+## What They're Trying to Achieve
+
+These trace back to organization-level jobs:
+
+| Product Job | Enables Org Job |
+|-------------|-----------------|
+| "[Product-specific job]" | "[Org job from manifesto]" |
+
+## The Problem
+
+[Pain points this product addresses]
+
+## The Solution
+
+[How this product solves those problems]
+
+## Product Principles
+
+These extend the organization's guiding principles:
+
+### [Principle Name]
+
+[Description]
+
+*Extends: "[Org principle]"*
+
+## Non-Goals
+
+These extend the organization's non-goals:
+
+- **[Non-goal].** [Explanation]
+```
+
 ## Output Format
 
 ```
 ## Organization Context
 
-See manifesto for shared personas, beliefs, and principles.
-[Link or note about manifesto.md location]
+From manifesto.md:
+- **Personas**: [list from manifesto]
+- **Core beliefs**: [key beliefs]
+- **Principles**: [list]
 
 ## Product: [Name]
 
 ### Who This Product Serves
 
 - **[Persona 1]**: [Product-specific description]
-- **[Persona 2]**: [Product-specific description]
+  ↳ Extends: [Org persona]
 
 ### What They're Trying to Achieve
 
-- "[Product-specific job 1]"
-- "[Product-specific job 2]"
+| Product Job | → Org Job |
+|-------------|-----------|
+| [job] | [org job it enables] |
 
-### Product Vision
+### Vision Summary
 
-[Summary of problem/solution from vision.md]
+[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]
 ```
 
+## Inheritance Rules
+
+- **Personas**: Product personas extend org personas with product-specific context
+- **Jobs**: Product jobs trace back to org-level jobs (show the connection)
+- **Beliefs**: Inherited from manifesto, never duplicated in vision
+- **Principles**: Product adds specific principles that extend org principles
+- **Non-Goals**: Product adds its own; org non-goals apply automatically
+
 ## 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
+- Product vision builds on organization manifesto - extend, don't duplicate
+- Every product persona should reference which org persona it extends
+- Every product job should show which org job it enables
+- Product principles should note which org principle they extend
 - 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