Files
architecture/commands/plan-issues.md
Hugo Nijhuis 1c0b6b3712 Add dependency management to issue workflows
Updated skills and commands to identify and formally link issue
dependencies using tea CLI:

Skills updated:
- issue-writing: Document deps in description + link with tea CLI
- backlog-grooming: Check for formal dependency links in checklist
- roadmap-planning: Link dependencies after creating issues

Commands updated:
- create-issue: Ask about and link dependencies for new issues
- plan-issues: Create in dependency order, link with tea issues deps add
- groom: Check dependency status, suggest missing links

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-07 16:35:39 +01:00

49 lines
1.6 KiB
Markdown

---
description: Plan and create issues for a feature or improvement. Breaks down work into well-structured issues with vision alignment.
argument-hint: <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 dependency order (blockers first)
8. **Link dependencies** using `tea issues deps add <issue> <blocker>` for each dependency
9. **Present summary** with links to created issues and dependency graph