Update /retro command to store learnings and create encoding issues

Restructured retro flow to:
1. Store learnings in learnings/ folder (historical + governance)
2. Create encoding issues to update skills/commands/agents
3. Cross-reference between learning files and issues
4. Handle both architecture and product repos differently

Key changes:
- Learning file template with Date, Context, Learning, Encoded In, Governance
- Encoding issue template referencing the learning file
- Encoding destinations table (skill/command/agent/manifesto/vision)
- Clear guidance for architecture vs product repo workflows
- Updated labels (learning instead of retrospective)

Closes #42

🤖 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/retro.md

@@ -5,9 +5,10 @@ argument-hint: [task-description]
 
 # Retrospective
 
-Capture learnings from completed AI-assisted work to improve the workflow and refine the product vision.
+Capture learnings from completed work. Learnings are stored for historical record and governance, then encoded into skills/commands/agents where Claude can use them.
 
 @~/.claude/skills/vision-management/SKILL.md
+@~/.claude/skills/gitea/SKILL.md
 
 ## Process
 
@@ -18,75 +19,108 @@ Capture learnings from completed AI-assisted work to improve the workflow and re
    - What worked well?
    - Any specific improvement ideas?
 
-3. **Analyze and categorize**: Group learnings into:
-   - **Prompt improvements**: Better instructions for commands/skills
-   - **Missing capabilities**: New commands or skills needed
-   - **Tool issues**: Problems with tea CLI, git, or other tools
-   - **Context gaps**: Missing documentation or skills
+3. **Identify learnings**: For each insight, determine:
+   - **What was learned**: The specific insight
+   - **Where to encode it**: Which skill, command, or agent should change?
+   - **Governance impact**: What does this mean for how we work?
 
-4. **Connect to vision** (if `vision.md` exists in the target repo):
-   - Did this work make progress on any vision goals?
-   - Did learnings reveal new priorities that should become goals?
-   - Did we discover something that should be a non-goal?
-   - Should the current focus shift based on what we learned?
+4. **Store the learning**: Create a learning file in the architecture repo:
 
-   If any vision updates are needed:
-   - Present suggested changes to `vision.md`
-   - Ask for approval
-   - Update the vision file and sync to Gitea
-
-5. **Generate improvement issues**: For each actionable improvement:
-   - Determine the appropriate milestone (see Milestone Categorization below)
-   - Create an issue in the AI repo with the milestone assigned:
-
-```bash
-tea issues create -r flowmade-one/ai --title "<title>" --description "<body>" --milestone "<milestone>"
-```
-
-## Milestone Assignment
-
-Before creating issues, fetch available milestones:
-
-```bash
-tea milestones -f title,description
-```
-
-For each issue, automatically assign to the most relevant milestone by matching:
-- Issue content/problem area → Milestone title and description
-- If no clear match, ask the user which milestone (goal) the issue supports
-- If no milestones exist, skip milestone assignment
-
-## Issue Format
-
-Use this structure for retrospective issues:
+   **File**: `learnings/YYYY-MM-DD-short-title.md`
 
    ```markdown
-## Context
-What task triggered this learning (brief).
+   # [Learning Title]
 
-## Problem / Observation
-What was the friction point or insight.
+   **Date**: YYYY-MM-DD
+   **Context**: [Task that triggered this learning]
 
-## Suggested Improvement
-Concrete, actionable change to make.
+   ## Learning
 
-## Affected Files
-- commands/xxx.md
-- skills/xxx/SKILL.md
+   [The specific insight - be concrete and actionable]
+
+   ## Encoded In
+
+   - Pending: Issue #XX to update [target skill/command/agent]
+
+   ## Governance
+
+   [What this means for how we work going forward]
    ```
 
+   ```bash
+   # Create the learning file in architecture repo
+   # If in architecture repo:
+   cat > learnings/YYYY-MM-DD-short-title.md << 'EOF'
+   [content]
+   EOF
+
+   # If in a different repo, note that learning should be added to architecture repo
+   ```
+
+5. **Create encoding issue**: Create an issue to encode the learning:
+
+   ```bash
+   tea issues create -r flowmade-one/ai \
+     --title "Encode learning: [brief description]" \
+     --description "## Learning Reference
+   See: learnings/YYYY-MM-DD-short-title.md
+
+   ## What to Encode
+   [The specific change to make]
+
+   ## Target
+   - [ ] \`skills/xxx/SKILL.md\` - [what to add/change]
+   - [ ] \`commands/xxx.md\` - [what to add/change]
+
+   ## Governance
+   [Why this matters]"
+   ```
+
+6. **Update learning file**: Add the issue reference to the "Encoded In" section.
+
+7. **Connect to vision**: Check if learning affects vision:
+   - **Architecture repo**: Does this affect `manifesto.md`? (beliefs, principles, non-goals)
+   - **Product repo**: Does this affect `vision.md`? (product direction, goals)
+
+   If vision updates are needed:
+   - Present suggested changes
+   - Ask for approval
+   - Update the appropriate file
+
+## Encoding Destinations
+
+| Learning Type | Encode In |
+|---------------|-----------|
+| How to use a tool | `skills/[tool]/SKILL.md` |
+| Workflow improvement | `commands/[command].md` |
+| Subtask behavior | `agents/[agent]/agent.md` |
+| Organization belief | `manifesto.md` |
+| Product direction | `vision.md` (in product repo) |
+
+## Architecture vs Product Repos
+
+**In the architecture repo**:
+- Learning files are created directly in `learnings/`
+- Issues are created in the same repo
+- Vision changes affect `manifesto.md`
+
+**In product repos**:
+- Learning files should be added to the architecture repo (not the product repo)
+- Issues are created in `flowmade-one/ai` (architecture repo)
+- Local vision changes affect `vision.md` in the product repo
+
 ## Labels
 
-Add appropriate labels:
-- `retrospective` - Always add this
+Add appropriate labels to encoding issues:
+- `learning` - Always add this
 - `prompt-improvement` - For command/skill text changes
-- `new-feature` - For new commands/skills
+- `new-feature` - For new commands/skills/agents
 - `bug` - For things that are broken
 
 ## Guidelines
 
-- Be specific and actionable - vague issues won't get fixed
-- One issue per improvement (don't bundle unrelated things)
-- Reference specific commands/skills when relevant
-- Keep issues small and focused
-- Skip creating issues for one-off edge cases that won't recur
+- **Be specific**: Vague learnings can't be encoded
+- **One learning per file**: Don't bundle unrelated insights
+- **Always encode**: A learning without encoding is just documentation
+- **Reference both ways**: Learning file → Issue, Issue → Learning file
+- **Skip one-offs**: Don't capture learnings for edge cases that won't recur

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 |
-|-------|---------|----------|
-| **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.
+Product vision inherits from and extends the organization manifesto.
 
 ## 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**:
-   - Ask the user if they want to create one
+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
+   - 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)
-     2. **Jobs to be done**: What are they trying to achieve?
-     3. **The problem**: What pain points exist today?
-     4. **The solution**: How does this product address their jobs?
-     5. **Guiding principles**: What beliefs guide decisions?
-     6. **Non-goals**: What are we explicitly NOT doing?
-   - Create `vision.md` (do NOT include goals/progress - that's milestones)
-   - Ask about initial goals tied to personas/jobs, create as Gitea milestones
+     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`
+   - Ask about initial goals, create as Gitea milestones
 
-3. **If vision exists**:
-   - Display the vision philosophy from `vision.md`
+4. **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 `$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]
-- **[Persona 2]**: [Brief description]
+See manifesto for shared personas, beliefs, and principles.
+[Link or note about manifesto.md location]
 
-## What They're Trying to Achieve
+## Product: [Name]
 
-- "[Job to be done 1]"
-- "[Job to be done 2]"
+### Who This Product Serves
 
-## 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
-- Personas and jobs to be done are foundational - everything traces back to them
-- Milestones are actionable goals - each should serve a specific persona's job
-- Assign issues to milestones to track progress
-- Use milestone descriptions for: persona, job, success criteria
-- Due dates on milestones are optional but help prioritization
-- If you can't tie work to a persona/job, question whether it should be done
+- 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