Files
architecture/commands/vision.md
Hugo Nijhuis 28242d44cc 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

79 lines
2.1 KiB
Markdown

---
description: View the product vision and goal progress. Manages vision.md and Gitea milestones.
argument-hint: [goals]
---
# Product Vision
@~/.claude/skills/vision-management/SKILL.md
@~/.claude/skills/gitea/SKILL.md
## Architecture
The vision system has two layers:
| Layer | Purpose | Location |
|-------|---------|----------|
| **vision.md** | North star philosophy (why, principles, non-goals) | File in repo root |
| **Milestones** | Goals with progress tracking | Gitea milestones |
Issues are assigned to milestones. Progress is visible through milestone completion.
## Process
1. **Check for existing vision**: Look for `vision.md` in the current repo root.
2. **If no vision exists**:
- Ask the user if they want to create one
- Guide them through the philosophy: purpose, principles, non-goals
- Create `vision.md` (do NOT include goals/progress - that's milestones)
- Ask about initial goals and create them as Gitea milestones
3. **If vision exists**:
- Display the vision philosophy from `vision.md`
- Show current milestones and their progress: `tea milestones`
- Check if `$1` specifies an action:
- `goals`: Manage milestones (add, close, view progress)
- If no action specified, just display the current state
4. **Managing Goals (milestones)**:
```bash
# List milestones with progress
tea milestones
# Create a new goal
tea milestones create --title "<goal>" --description "<success criteria>"
# View issues in a milestone
tea milestones issues <milestone-name>
# Close a completed goal
tea milestones close <milestone-name>
```
## Output Format
```
## Vision
[Summary of vision.md purpose/principles]
## Goals (Milestones)
| Goal | Progress | Due |
|------|----------|-----|
| [title] | 3/5 issues | [date] |
## Current Focus
[Open milestones with nearest due dates or most activity]
```
## Guidelines
- vision.md is the stable "why" document - update rarely
- Milestones are the actionable goals - create/close as needed
- Assign issues to milestones to track progress
- Use milestone descriptions for success criteria
- Due dates on milestones are optional but help prioritization