Hugo Nijhuis
9e1ca55196
Transforms the product-manager from a reactive backlog manager into a vision-driven system with continuous improvement capabilities. New components: - vision-management skill: How to create, maintain, and evolve product vision - /vision command: View, create, or update product vision (syncs to Gitea) - /improve command: Identify gaps between vision goals and backlog Enhanced existing components: - product-manager agent: Now vision-aware with strategic prioritization - /retro command: Connects learnings back to vision updates - /plan-issues command: Shows vision alignment for planned work The vision lives in two places: vision.md (source of truth) and a Gitea issue labeled "vision" for integration with the issue workflow. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
78 lines
2.4 KiB
Markdown
78 lines
2.4 KiB
Markdown
---
|
|
description: Run a retrospective on completed work. Captures learnings, creates improvement issues, and updates product vision.
|
|
argument-hint: [task-description]
|
|
---
|
|
|
|
# Retrospective
|
|
|
|
Capture learnings from completed AI-assisted work to improve the workflow and refine the product vision.
|
|
|
|
@~/.claude/skills/vision-management/SKILL.md
|
|
|
|
## 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. **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?
|
|
|
|
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, 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
|