Skip to content
Skills Library
Management & product · Planning

Tasks

/Tasks

Generate granular task breakdowns from implementation plans with TDD ordering, parallel task marking, and sequential numbering. USE WHEN tasks, task breakdown, todo list, implementation tasks, work items, actionable steps, generate tasks.

Licence
MIT
Last repository change
21.08.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Generate granular task breakdowns from implementation plans with TDD ordering, parallel task marking, and sequential numbering. USE WHEN tasks, task breakdown, todo list, implementation tasks, work items, actionable steps, generate tasks.

Original author description

Generate granular task breakdowns from implementation plans with TDD ordering, parallel task marking, and sequential numbering. USE WHEN tasks, task breakdown, todo list, implementation tasks, work items, actionable steps, generate tasks.

How it works

  1. Customization
  2. Prerequisites
  3. Workflow Routing
  4. Template Selection
  5. Plan Discovery
  6. Task Format
  7. Output
  8. Examples
Original SKILL.md headings · 59 lines, 202 words
SKILL.md preview
---
name: Tasks
description: Generate granular task breakdowns from implementation plans with TDD ordering, parallel task marking, and sequential numbering. USE WHEN tasks, task breakdown, todo list, implementation tasks, work items, actionable steps, generate tasks.
---

# Tasks

Break implementation plans into executable, TDD-ordered tasks with parallel marking and dependency tracking.

## Customization

**Before executing, check for user customizations at:**
`~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Tasks/`

If this directory exists, load and apply any PREFERENCES.md configurations. If not, proceed with defaults.

## Prerequisites

1. LifeOS must be installed. Check `~/.claude/LIFEOS/VERSION`.
2. Foundation must exist at `/directive/foundation.md`.
3. A plan must exist in `specs/` directory.

## Workflow Routing

| Workflow | Trigger | File |
|----------|---------|------|
| **GenerateTasks** | Any invocation | `Workflows/GenerateTasks.md` |

## Template Selection

Based on foundation type:
- **Default**: `Templates/DefaultTasks.md`
- **JHipster**: `Templates/JHipsterTasks.md`
- **MuleSoft**: `Templates/MuleSoftTasks.md`

## Plan Discovery

Scans `specs/` for folders with `plan.md` but no `tasks.md`. If multiple found, asks user.

## Task Format

- Sequential numbering: T001, T002, T003...
- Parallel marker: `[P]` for tasks on different files with no dependencies
- TDD order: Tests come before implementation
- Phases: Setup, Tests, Core, Integration, Polish
- Each task includes exact file path

## Output

Tasks are written to: `specs/[YYYYMMDD-slug]/tasks.md`

## Examples

**Example 1: Generate tasks**
```
User: "/buddy:tasks"
-> Discovers specs/20260402-user-authentication/plan.md (no tasks.md)
-> Reads plan.md, spec.md, and all design documents
-> Generates TDD-ordered tasks: T001-T045
-> Marks parallel tasks with [P]
-> Writes to specs/20260402-user-authentication/tasks.md
```
Files in this package (3)
  • SKILL.md 2 KB
  • Templates/DefaultTasks.md 2 KB
  • Workflows/GenerateTasks.md 4 KB

Versions

RepositoryScoreLicence
This page · rsts-dev/claude-buddy-marketplace95MIT
ericrisco/rsc-harness100MIT
komdosh/komnet100MIT
komdosh/komnet100MIT
maribol/overvibe100MIT
nikicat/claude-tasks100MIT
shenxingy/clade100MIT
xobotyi/cc-foundry100MIT
lauradfarbo/chief-of-staff100MIT

Database snapshot: 13.11.2026 · package version 559fe7fc0a37 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91implementation-plan
    Use when a user story or simple epic needs to be broken into atomic, TDD-driven implementation tasks with architectural review, or when planning the TDD task breakdown for a specific story or task ticket. Produces an ordered task list with explicit RED-test specs, identifies…
  • 100breakdown
    Use when a feature with a spec and a plan needs its ordered task list: \"break this into tasks\", \"make the task list\", \"what are the steps to build this?\", \"generate tasks.md\", a feature folder with plan.md and no tasks.md, or a task list made stale by a spec or plan…
  • 100planning-and-task-breakdown
    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
  • 100planning-and-task-breakdown
    Breaks work into ordered tasks. Use when you have a spec and need implementable tasks, when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
  • 100planning-and-task-breakdown
    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
  • 100planning-and-task-breakdown
    Decompose specs into small, ordered tasks with acceptance criteria and verification steps. Use when you have requirements and need an implementable plan or task list. Triggers: "break down tasks", "implementation plan", "task breakdown", "plan mode".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.