flowmade-one/architecture
3
0
Fork 0
Code Issues 15 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Add /retro command for self-learning workflow

Browse Source 
Captures learnings from completed AI-assisted work and creates
improvement issues in the AI repo. Creates a feedback loop where
friction points and insights get tracked as actionable issues.

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Hugo Nijhuis
2025-12-31 15:20:32 +01:00
parent 91d6ff5491
commit 0b8f830921
2 changed files with 65 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
CLAUDE.md
View File

@@ -45,6 +45,7 @@ tea logins add --name flowmade --url https://git.flowmade.one --token <your-toke
| `/dashboard` | Show open issues and PRs | | `/dashboard` | Show open issues and PRs |
| `/review-pr <n>` | Review PR with diff and comments | | `/review-pr <n>` | Review PR with diff and comments |
| `/create-issue` | Create single or batch issues | | `/create-issue` | Create single or batch issues |
| `/retro` | Capture learnings from completed work, create improvement issues |
## Usage ## Usage

64
commands/retro.md Normal file
View File

@@ -0,0 +1,64 @@
---
description: Run a retrospective on completed work. Captures learnings and creates improvement issues in the AI repo.
argument-hint: [task-description]
---
# Retrospective
Capture learnings from completed AI-assisted work to improve the workflow.
## Process
1. **Gather context**: If $1 is provided, use it as the task description. Otherwise, ask the user what task was just completed.
2. **Reflect on the work**: Ask the user (or summarize from conversation context if obvious):
- What friction points were encountered?
- 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
4. **Generate improvement issues**: For each actionable improvement, create an issue in the AI repo using:
```bash
tea issues create -r flowmade-one/ai --title "<title>" --description "<body>"
```
## Issue Format
Use this structure for retrospective issues:
```markdown
## Context
What task triggered this learning (brief).
## Problem / Observation
What was the friction point or insight.
## Suggested Improvement
Concrete, actionable change to make.
## Affected Files
- commands/xxx.md
- skills/xxx/SKILL.md
```
## Labels
Add appropriate labels:
- `retrospective` - Always add this
- `prompt-improvement` - For command/skill text changes
- `new-feature` - For new commands/skills
- `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