Starting from a Redmine ticket, generate an executable development plan.
Prerequisites
This skill depends on the Redmine API access capability provided by the redmine-search skill.
Workflow
1. Obtain ticket information
Obtain ticket details via the Redmine API:
GET /issues/{issue_id}.json?include=journals,relations,children
Extract key information:
- TitleandDescription: Understand the requirements overview
- Tracker type: Feature / Bug / Todo
- PriorityandDue date: Determine urgency
- Related tickets: Understand context and dependencies
- Attachment list: Specification documents, design diagrams, etc.
2. Requirements analysis
Adopt different analysis strategies based on the ticket type:
| Type | Analysis focus | Output |
|---|---|---|
| Feature | Functional scope, UI design, data flow, interface requirements | Feature implementation plan |
| Bug | Problem reproduction, root cause analysis, impact scope | Hand over to BugHunter |
| Todo | Specific task content, completion criteria | Task list |
3. Context collection
Automatically execute：
- Identify the project tech stack (package.json)
- Search the codebase for related files and modules (based on ticket keywords)
- Check whether there are related specification document attachments (prompt the user to provide them)
- View related tickets to understand the full context
4. Task breakdown
Break down the requirements into executable development steps:
## 开发计划
### 票据信息
- **ID**: #12345
- **类型**: 课题
- **标题**: [标题]
- **优先级**: [优先级]
- **截止日期**: [日期]
### 需求理解
[一段话概括需求核心]
### 涉及模块
- `xxx` — [修改说明]
- `yyy` — [修改说明]
- `zzz` — [修改说明]
### 开发步骤
#### Step 1: [步骤名称]
- 预计耗时：[时间]
- 具体内容：[详细说明]
- 相关文件：[文件列表]
#### Step 2: [步骤名称]
...
### 注意事项
- [需要确认的点]
- [可能的风险]
### 式样书相关
- 需要参考的式样书：[文件名或附件]
- 建议使用 `/excel-to-markdown` 转换后作为上下文
5. Link with other Skills
Based on the development plan, prompt the user about skills that can be used:
| Development phase | Recommended Skill |
|---|---|
| Specification document reading | /excel-to-markdown(If the specifications provided by the user are clear enough, this skill is not needed) |
| Create component | /component-scaffolder(triggers component-scaffolder) |
| API integration | /api-type-generator(triggers api-type-generator) |
| Bug fix | BugHunter subagent |
| Code review | /code-review(triggers code-review) |
| Debug issues | /smart-debugger(triggers smart-debugger) |
Output principles
- Executable: Each step has specific operation content
- Estimable: Provide a rough time estimate
- Prioritized: Mark which steps can be parallelized and which have dependencies
- Risk annotation: Mark uncertain points and content that needs confirmation