How do I install the Generate Tasks skill?

Run npx skillmds@latest add duboc/generate-tasks in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Generate Tasks safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Generate Tasks?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Generate Tasks free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Generate Tasks?

duboc (@duboc) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Generate Tasks by duboc — Agent Skill

Name: Generate Tasks
Rating: 4.2 (5 reviews)
Author: duboc

File contents

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`

# 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

---name: generate-tasksdescription: Break down a feature specification into implementable tasks. Use when preparing to implement a specified feature.---# Generate Task BreakdownBreak 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### DescriptionWrite 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

Frequently asked questions

Generate Tasks