Hugo Nijhuis
b8ca2386fa
Skills have only ~20% auto-activation rate when referenced by name. Using @~/.claude/skills/*/SKILL.md guarantees skill content is loaded. Updated all commands to use file references instead of "Use the X skill". Updated docs/writing-commands.md with new pattern and examples. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
37 lines
1.0 KiB
Markdown
37 lines
1.0 KiB
Markdown
---
|
|
description: Plan and create issues for a feature or improvement. Breaks down work into well-structured issues.
|
|
argument-hint: <feature-description>
|
|
---
|
|
|
|
# Plan Feature: $1
|
|
|
|
@~/.claude/skills/gitea/SKILL.md
|
|
@~/.claude/skills/roadmap-planning/SKILL.md
|
|
@~/.claude/skills/issue-writing/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:
|
|
- Each issue should be independently completable
|
|
- Clear dependencies between issues
|
|
- Appropriate scope (not too big, not too small)
|
|
|
|
4. **Present the plan**:
|
|
```
|
|
## Proposed Issues for: $1
|
|
|
|
1. [Title] - Brief description
|
|
Dependencies: none
|
|
|
|
2. [Title] - Brief description
|
|
Dependencies: #1
|
|
|
|
3. [Title] - Brief description
|
|
Dependencies: #1, #2
|
|
```
|
|
|
|
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
|