Files

Use Gitea milestones for goal tracking instead of vision issue

Refactored the vision system to separate concerns:
- vision.md remains the stable "north star" philosophy document
- Gitea milestones now track goals with automatic progress via issue counts
- Updated /vision, /retro, and /create-issue commands to auto-assign milestones

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-01 22:22:06 +01:00

2.9 KiB

Raw Blame History

description, argument-hint

description

argument-hint

Run a retrospective on completed work. Captures learnings, creates improvement issues, and updates product vision.

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

Gather context: If $1 is provided, use it as the task description. Otherwise, ask the user what task was just completed.
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?
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
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
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:

tea issues create -r flowmade-one/ai --title "<title>" --description "<body>" --milestone "<milestone>"

Milestone Assignment

Before creating issues, fetch available milestones:

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:

## 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

2.9 KiB Raw Blame History