Update /retro command to store learnings and create encoding issues #42

New Issue

HugoNijhuis · 2026-01-07T18:52:06Z

HugoNijhuis commented

2026-01-07 18:52:06 +00:00

Summary

Update the /retro command to:

Store learnings in the learnings/ folder (historical + governance)
Create issues to encode learnings into skills/commands/agents (actionable)

Updated Flow

Gather context: What task was completed
Reflect: What worked, what didn't, insights gained
Categorize learning:
- Where should this be encoded? (skill/command/agent)
- What governance does this establish?
Store learning: Write to learnings/YYYY-MM-DD-title.md
Create encoding issue: Issue to update the appropriate skill/command/agent
Vision connection: Does this affect manifesto or product vision?

Learning File Creation

# [Learning Title]

**Date**: YYYY-MM-DD
**Context**: [Task that triggered this]

## Learning
[The insight]

## Encoded In
- Pending: Issue #XX to update [target]

## Governance
[What this means for how we work]

Dependencies

Depends on #39 (learnings folder must exist)

Acceptance Criteria

/retro creates learning file in learnings/
/retro creates issue to encode learning into skill/command/agent
Learning file references the encoding issue
Encoding issue references the learning file
Flow handles both architecture repo and product repos

## Summary Update the `/retro` command to: 1. Store learnings in the `learnings/` folder (historical + governance) 2. Create issues to encode learnings into skills/commands/agents (actionable) ## Updated Flow 1. **Gather context**: What task was completed 2. **Reflect**: What worked, what didn't, insights gained 3. **Categorize learning**: - Where should this be encoded? (skill/command/agent) - What governance does this establish? 4. **Store learning**: Write to `learnings/YYYY-MM-DD-title.md` 5. **Create encoding issue**: Issue to update the appropriate skill/command/agent 6. **Vision connection**: Does this affect manifesto or product vision? ## Learning File Creation ```markdown # [Learning Title] **Date**: YYYY-MM-DD **Context**: [Task that triggered this] ## Learning [The insight] ## Encoded In - Pending: Issue #XX to update [target] ## Governance [What this means for how we work] ``` ## Dependencies - Depends on #39 (learnings folder must exist) ## Acceptance Criteria - [ ] /retro creates learning file in learnings/ - [ ] /retro creates issue to encode learning into skill/command/agent - [ ] Learning file references the encoding issue - [ ] Encoding issue references the learning file - [ ] Flow handles both architecture repo and product repos

HugoNijhuis referenced this issue

2026-01-07 18:52:27 +00:00

Rename repo from 'ai' to 'architecture' #44

HugoNijhuis added a new dependency 2026-01-07 18:52:39 +00:00

#39 Create learnings/ folder with structure and template

HugoNijhuis added a new dependency 2026-01-07 18:52:40 +00:00

#44 Rename repo from 'ai' to 'architecture'

HugoNijhuis referenced this issue

2026-01-07 18:52:51 +00:00

Consider renaming repo to 'architecture' to include engineering patterns #37

HugoNijhuis referenced this issue from a commit

2026-01-07 19:27:34 +00:00