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>

skills/vision-management/SKILL.md

@@ -15,7 +15,7 @@ How to create, maintain, and evolve organizational direction at two levels: mani
 | **Product** | `vision.md` | Product-specific personas, jobs, solution | `/vision` | Product repos |
 | **Goals** | Gitea milestones | Measurable progress toward vision | `/vision goals` | Per repo |
 
-Product vision inherits from and extends the organization manifesto.
+Product vision **inherits from and extends** the organization manifesto - it should never duplicate.
 
 ---
 
@@ -74,32 +74,54 @@ What the organization explicitly does NOT do.
 
 ## Vision (Product Level)
 
-The vision defines what a specific product does. It lives in each product repo and extends the manifesto.
+The vision defines what a specific product does. It lives in each product repo and **extends the manifesto**.
 
 ### Vision Structure
 
 ```markdown
 # Vision
 
+This product vision builds on the [organization manifesto](link-to-manifesto).
+
 ## Who This Product Serves
-Product-specific personas (may extend org personas).
-- **Persona Name**: Product-specific context
+
+### [Persona Name]
+
+[Product-specific description]
+
+*Extends: [Org persona] (from manifesto)*
 
 ## What They're Trying to Achieve
-Product-specific jobs to be done.
-- "Help me [outcome] without [pain]"
+
+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.
+
+[Pain points this product addresses]
 
 ## The Solution
-How this product solves those problems.
+
+[How this product solves those problems]
 
 ## Product Principles
-Product-specific principles (beyond org principles).
+
+These extend the organization's guiding principles:
+
+### [Principle Name]
+
+[Description]
+
+*Extends: "[Org principle]"*
 
 ## Non-Goals
-What this product explicitly does NOT do.
+
+These extend the organization's non-goals:
+
+- **[Non-goal].** [Explanation]
 ```
 
 ### When to Update Vision
@@ -111,51 +133,58 @@ What this product explicitly does NOT do.
 
 ### Creating a Product Vision
 
-1. Reference the organization manifesto
-2. Define product-specific personas (can extend org personas)
-3. Identify product-specific jobs to be done
+1. **Start with the manifesto** - read it first
+2. Define product personas that extend org personas
+3. Identify product jobs that trace back to org jobs
 4. Articulate the problem this product solves
 5. Define the solution approach
-6. Set product-specific principles (if any)
+6. Set product-specific principles (noting what they extend)
 7. Document product non-goals
 8. Create initial milestones
 
 ---
 
-## Relationship: Manifesto → Vision
+## Inheritance Model
 
 ```
-Manifesto (org)          Vision (product)
-├── Shared Personas  →   Product Personas (more specific)
-├── Org Jobs         →   Product Jobs (subset/extension)
-├── Beliefs          →   (inherited, not duplicated)
-├── Principles       →   Product Principles (additional)
-└── Non-Goals        →   Product Non-Goals (additional)
+Manifesto (org)              Vision (product)
+├── Personas            →    Product Personas (extend with specifics)
+├── Jobs                →    Product Jobs (trace back to org jobs)
+├── Beliefs             →    (inherited, never duplicated)
+├── Principles          →    Product Principles (extend, note source)
+└── Non-Goals           →    Product Non-Goals (additive)
 ```
 
-### Inheritance Model
+### Inheritance Rules
 
-- **Personas**: Product personas can be more specific versions of org personas
-- **Jobs**: Product jobs should trace back to org-level jobs
-- **Beliefs**: Inherited from manifesto, not duplicated in vision
-- **Principles**: Product can add specific principles; org principles apply automatically
-- **Non-Goals**: Product adds its own; org non-goals apply automatically
+| Component | Rule | Format |
+|-----------|------|--------|
+| **Personas** | Extend with product-specific context | `*Extends: [Org persona] (from manifesto)*` |
+| **Jobs** | Trace back to org-level jobs | Table with Product Job → Org Job columns |
+| **Beliefs** | Inherited automatically | Never include in vision |
+| **Principles** | Add product-specific, note what they extend | `*Extends: "[Org principle]"*` |
+| **Non-Goals** | Additive | Org non-goals apply automatically |
 
 ### Example
 
 **Manifesto** (organization):
 ```markdown
 ## Who We Serve
-- **Solo Developer**: Individual shipping side projects, time-constrained
+- **Agencies & Consultancies**: Teams building solutions for clients
 ```
 
-**Vision** (product - e.g., CLI tool):
+**Vision** (product - architecture tooling):
 ```markdown
 ## Who This Product Serves
-- **Solo Developer (CLI user)**: Uses terminal daily, prefers keyboard over GUI
+
+### Flowmade Developers
+
+The team building Flowmade's platform. They need efficient, consistent AI workflows.
+
+*Extends: Agencies & Consultancies (from manifesto) - we are our own first customer.*
 ```
 
-The product persona extends the org persona with product-specific context.
+The product persona extends the org persona with product-specific context and explicitly notes the connection.
 
 ---
 
@@ -180,8 +209,8 @@ Success: /commit and /pr commands handle 80% of workflows"
 ### Milestone-to-Vision Alignment
 
 Every milestone should trace to:
-- A persona (from vision or manifesto)
-- A job to be done (from vision)
+- A persona (from vision, which extends manifesto)
+- A job to be done (from vision, which traces to manifesto)
 - A measurable outcome
 
 ---
@@ -218,7 +247,7 @@ Manifesto → Vision → Milestones → Issues → Work → Retro → (updates)
 ```
 
 1. **Manifesto** defines organizational identity (very stable)
-2. **Vision** defines product direction (stable)
+2. **Vision** defines product direction, extends manifesto (stable)
 3. **Milestones** define measurable goals (evolve)
 4. **Issues** are work items toward goals
 5. **Work** implements the issues
@@ -232,9 +261,11 @@ Manifesto → Vision → Milestones → Issues → Work → Retro → (updates)
 | Question | Answer |
 |----------|--------|
 | Where do shared personas live? | `manifesto.md` in architecture repo |
-| Where do product personas live? | `vision.md` in product repo |
-| Where do beliefs live? | `manifesto.md` only (inherited) |
+| Where do product personas live? | `vision.md` in product repo (extend org personas) |
+| Where do beliefs live? | `manifesto.md` only (inherited, never duplicated) |
 | Where do goals live? | Gitea milestones (per repo) |
 | What command for org vision? | `/manifesto` |
 | What command for product vision? | `/vision` |
 | What repo for learnings? | Architecture repo |
+| How do product jobs relate to org jobs? | They trace back (show in table) |
+| How do product principles relate? | They extend (note the source) |