Files
architecture/commands/plan-issues.md
Hugo Nijhuis 9e1ca55196 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>
2026-01-01 21:57:28 +01:00

1.6 KiB

description, argument-hint
description argument-hint
Plan and create issues for a feature or improvement. Breaks down work into well-structured issues with vision alignment. <feature-description>

Plan Feature: $1

@/.claude/skills/gitea/SKILL.md @/.claude/skills/roadmap-planning/SKILL.md @/.claude/skills/issue-writing/SKILL.md @/.claude/skills/vision-management/SKILL.md

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

    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