Hugo Nijhuis
68675a7e12
- Replace fj CLI with tea CLI across all commands - Create new gitea skill, remove forgejo skill - Update all agents to use gitea skill - Update commands to use skill-based approach (reference skills instead of embedding CLI commands) - Update all documentation (README, ARCHITECTURE, VISION, writing guides) - Swap git remotes: origin now points to git.flowmade.one (Gitea) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
35 lines
999 B
Markdown
35 lines
999 B
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
|
|
|
|
Use the gitea, roadmap-planning, and issue-writing skills.
|
|
|
|
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
|