Add vision-driven continuous improvement to product-manager
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>
This commit is contained in:
82
commands/improve.md
Normal file
82
commands/improve.md
Normal file
@@ -0,0 +1,82 @@
|
||||
---
|
||||
description: Identify improvement opportunities based on product vision. Analyzes gaps between vision goals and current backlog.
|
||||
---
|
||||
|
||||
# Improvement Analysis
|
||||
|
||||
@~/.claude/skills/vision-management/SKILL.md
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
@~/.claude/skills/issue-writing/SKILL.md
|
||||
@~/.claude/skills/roadmap-planning/SKILL.md
|
||||
|
||||
## Process
|
||||
|
||||
1. **Read the vision**: Load `vision.md` from the repo root.
|
||||
- If no vision exists, suggest running `/vision` first
|
||||
|
||||
2. **Fetch current backlog**: Get all open issues from Gitea using `tea issues`
|
||||
|
||||
3. **Analyze alignment**:
|
||||
|
||||
For each vision goal, check:
|
||||
- Are there issues supporting this goal?
|
||||
- Is there recent activity/progress?
|
||||
- Are issues blocked or stalled?
|
||||
|
||||
For each open issue, check:
|
||||
- Does it align with a vision goal?
|
||||
- Is it supporting the current focus?
|
||||
|
||||
4. **Identify gaps and opportunities**:
|
||||
|
||||
- **Unsupported goals**: Vision goals with no issues
|
||||
- **Stalled goals**: Goals with issues but no recent progress
|
||||
- **Orphan issues**: Issues that don't support any goal
|
||||
- **Focus misalignment**: Issues not aligned with current focus getting priority
|
||||
- **Missing non-goals**: Patterns suggesting things we should explicitly avoid
|
||||
|
||||
5. **Present findings**:
|
||||
|
||||
```
|
||||
## Vision Alignment Report
|
||||
|
||||
### Goals Coverage
|
||||
- Goal 1: [status] - N issues, [progress]
|
||||
- Goal 2: [status] - N issues, [progress]
|
||||
|
||||
### Gaps Identified
|
||||
1. [Gap description]
|
||||
Suggestion: [concrete action]
|
||||
|
||||
2. [Gap description]
|
||||
Suggestion: [concrete action]
|
||||
|
||||
### Orphan Issues
|
||||
- #N: [title] - No goal alignment
|
||||
|
||||
### Recommended Actions
|
||||
1. [Action with rationale]
|
||||
2. [Action with rationale]
|
||||
```
|
||||
|
||||
6. **Offer to take action**:
|
||||
|
||||
For unsupported goals:
|
||||
- Ask if user wants to plan issues for the gap
|
||||
- If yes, run the `/plan-issues` workflow for that goal
|
||||
- This breaks down the goal into concrete, actionable issues
|
||||
|
||||
For other findings:
|
||||
- Re-prioritize issues based on focus
|
||||
- Close or re-scope orphan issues
|
||||
- Update vision with suggested changes
|
||||
|
||||
Always ask for approval before making changes.
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Focus on actionable improvements, not just observations
|
||||
- Prioritize suggestions by impact on vision goals
|
||||
- Keep suggestions specific and concrete
|
||||
- One issue per improvement (don't bundle)
|
||||
- Reference specific goals when suggesting new issues
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
description: Plan and create issues for a feature or improvement. Breaks down work into well-structured issues.
|
||||
description: Plan and create issues for a feature or improvement. Breaks down work into well-structured issues with vision alignment.
|
||||
argument-hint: <feature-description>
|
||||
---
|
||||
|
||||
@@ -8,29 +8,41 @@ argument-hint: <feature-description>
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
@~/.claude/skills/roadmap-planning/SKILL.md
|
||||
@~/.claude/skills/issue-writing/SKILL.md
|
||||
@~/.claude/skills/vision-management/SKILL.md
|
||||
|
||||
1. **Understand the feature**: Analyze what "$1" involves
|
||||
2. **Explore the codebase** if needed to understand context
|
||||
3. **Break down** into discrete, actionable issues:
|
||||
1. **Check vision context**: If `vision.md` exists, read it to understand current goals and focus
|
||||
2. **Understand the feature**: Analyze what "$1" involves
|
||||
3. **Explore the codebase** if needed to understand context
|
||||
4. **Break down** into discrete, actionable issues:
|
||||
- Each issue should be independently completable
|
||||
- Clear dependencies between issues
|
||||
- Appropriate scope (not too big, not too small)
|
||||
|
||||
4. **Present the plan**:
|
||||
5. **Present the plan** (include vision alignment if vision exists):
|
||||
```
|
||||
## Proposed Issues for: $1
|
||||
|
||||
Vision Alignment: Supports [Goal N: description]
|
||||
|
||||
1. [Title] - Brief description
|
||||
Dependencies: none
|
||||
Supports: Goal N
|
||||
|
||||
2. [Title] - Brief description
|
||||
Dependencies: #1
|
||||
Supports: Goal N
|
||||
|
||||
3. [Title] - Brief description
|
||||
Dependencies: #1, #2
|
||||
Supports: Goal N
|
||||
```
|
||||
|
||||
5. **Ask for approval** before creating issues
|
||||
6. **Create issues** in order
|
||||
7. **Update dependencies** with actual issue numbers after creation
|
||||
8. **Present summary** with links to created issues
|
||||
If the feature doesn't align with any vision goal, note this and ask if:
|
||||
- The vision should be updated to include this as a goal
|
||||
- This should be added as a non-goal
|
||||
- Proceed anyway (with justification)
|
||||
|
||||
6. **Ask for approval** before creating issues
|
||||
7. **Create issues** in order
|
||||
8. **Update dependencies** with actual issue numbers after creation
|
||||
9. **Present summary** with links to created issues
|
||||
|
||||
@@ -1,11 +1,13 @@
|
||||
---
|
||||
description: Run a retrospective on completed work. Captures learnings and creates improvement issues in the AI repo.
|
||||
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.
|
||||
Capture learnings from completed AI-assisted work to improve the workflow and refine the product vision.
|
||||
|
||||
@~/.claude/skills/vision-management/SKILL.md
|
||||
|
||||
## Process
|
||||
|
||||
@@ -22,7 +24,18 @@ Capture learnings from completed AI-assisted work to improve the workflow.
|
||||
- **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:
|
||||
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>"
|
||||
|
||||
72
commands/vision.md
Normal file
72
commands/vision.md
Normal file
@@ -0,0 +1,72 @@
|
||||
---
|
||||
description: View, create, or update the product vision. Manages vision.md and syncs to Gitea.
|
||||
argument-hint: [update|goals|focus]
|
||||
---
|
||||
|
||||
# Product Vision
|
||||
|
||||
@~/.claude/skills/vision-management/SKILL.md
|
||||
@~/.claude/skills/gitea/SKILL.md
|
||||
|
||||
## 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:
|
||||
- Purpose: Why does this product exist?
|
||||
- Goals: 3-5 measurable outcomes with success metrics
|
||||
- Current focus: Which 1-2 goals are priorities now?
|
||||
- Non-goals: What are you explicitly NOT doing?
|
||||
- Create `vision.md` with the vision document structure
|
||||
- Create a Gitea issue labeled `vision` with the same content
|
||||
|
||||
3. **If vision exists**:
|
||||
- Display the current vision
|
||||
- Check if $1 specifies an action:
|
||||
- `update`: General update to the vision
|
||||
- `goals`: Add, modify, or complete goals
|
||||
- `focus`: Change the current focus area
|
||||
- If no action specified, ask what the user wants to do:
|
||||
- View only (done)
|
||||
- Update goals
|
||||
- Change focus
|
||||
- Update progress
|
||||
- Add non-goals
|
||||
- Make the requested changes
|
||||
- Update `vision.md`
|
||||
- Sync changes to the Gitea vision issue
|
||||
|
||||
4. **Sync to Gitea**:
|
||||
- Find existing issue with `vision` label: `tea issues -l vision`
|
||||
- If exists: Update the issue description
|
||||
- If not: Create new issue with `vision` label
|
||||
|
||||
## Output Format
|
||||
|
||||
When displaying the vision, show it clearly:
|
||||
|
||||
```
|
||||
## Current Vision
|
||||
|
||||
**Purpose**: [purpose]
|
||||
|
||||
**Goals**:
|
||||
1. [Goal] - [Metric] [Progress indicator]
|
||||
2. [Goal] - [Metric] [Progress indicator]
|
||||
|
||||
**Current Focus**: [focus area]
|
||||
|
||||
**Non-Goals**: [list]
|
||||
|
||||
**Last Updated**: [date]
|
||||
```
|
||||
|
||||
## Guidelines
|
||||
|
||||
- Keep goals specific and measurable
|
||||
- Limit to 3-5 active goals
|
||||
- Current focus should be 1-2 goals max
|
||||
- Update "Last Updated" on every change
|
||||
- Always sync to Gitea after changes
|
||||
Reference in New Issue
Block a user