# Generate Tasks

> Break down a feature specification into implementable tasks. Use when preparing to implement a specified feature.

- Skill: `duboc/generate-tasks` (Agent Skill)
- Install (CLI): `npx skillmds@latest add duboc/generate-tasks`
- Raw SKILL.md: https://api.skillmd.com/api/skills/duboc/generate-tasks/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: duboc (https://skillmd.com/u/duboc)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/duboc/generate-tasks

---


# Generate Task Breakdown

Break down a feature specification into concrete, implementable tasks.

## Workflow

### 1. Read Specification
- Read `docs/specs/[feature-name].md`
- Understand all requirements
- Identify dependencies

### 2. Create Task Breakdown

#### Output: `docs/tasks/[feature-name]-tasks.md`

```markdown
# Task Breakdown: [Feature Name]

## Progress Summary
- **Total Steps**: X
- **Completed**: Y
- **Current**: Step Z - [Description]
- **Status**: Not Started | In Progress | Blocked | Complete

---

## Step 1: [Task Title]
**Complexity**: Low | Medium | High
**Status**: Pending | In Progress | Complete

### Description
[What needs to be done]

### Subtasks
- [ ] 1.1 [Subtask description]
- [ ] 1.2 [Subtask description]
- [ ] 1.3 [Subtask description]

### Implementation Notes
[Technical guidance, patterns to follow]

### Acceptance Criteria
- [ ] [Testable criterion]

---

## Step 2: [Task Title]
**Complexity**: Low | Medium | High
**Status**: Pending | In Progress | Complete

### Description
[What needs to be done]

### Subtasks
- [ ] 2.1 [Subtask description]
- [ ] 2.2 [Subtask description]

### Dependencies
- Requires Step 1 to be complete

### Implementation Notes
[Technical guidance]

### Acceptance Criteria
- [ ] [Testable criterion]

---

## Step 3: Write Tests
**Complexity**: Medium
**Status**: Pending

### Description
Write comprehensive tests for the feature

### Subtasks
- [ ] 3.1 Unit tests for ViewModel
- [ ] 3.2 Unit tests for Service
- [ ] 3.3 Integration tests
- [ ] 3.4 UI tests for critical paths

### Acceptance Criteria
- [ ] 80%+ code coverage for feature
- [ ] All tests passing

---

## Changes Log
| Date | Step | Change | Author |
|------|------|--------|--------|
| [Date] | 1 | Initial creation | [Name] |

## Blockers
- [ ] [Blocker description] - [Resolution plan]

## Definition of Done
- [ ] All tasks complete
- [ ] Tests passing
- [ ] Code reviewed
- [ ] Documentation updated
- [ ] Merged to main
```

### 3. Prioritize Tasks
- Order by dependencies
- Consider parallel work opportunities
- Identify blockers early

### 4. Estimate Complexity
- Low: < 2 hours, straightforward
- Medium: 2-4 hours, some complexity
- High: 4+ hours, complex or uncertain