architecture

Files

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>

2026-01-07 20:27:29 +01:00

create-issue.md

Add dependency management to issue workflows

2026-01-07 16:35:39 +01:00

dashboard.md

Use @ file references to include skills in commands

2026-01-01 11:09:26 +01:00

groom.md

Add dependency management to issue workflows

2026-01-07 16:35:39 +01:00

improve.md

Add vision-driven continuous improvement to product-manager