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.
- Author
- rsts-dev ↗
- Repository
- claude-buddy-marketplace ↗
- Licence
- MIT
- Last repository change
- 21.08.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.08.2026, without references to retired models or APIs.
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
- Customization
- Prerequisites
- Workflow Routing
- Template Selection
- Plan Discovery
- Task Format
- Output
- Examples
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
| Repository | Score | Licence |
|---|---|---|
| This page · rsts-dev/claude-buddy-marketplace | 95 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| komdosh/komnet | 100 | MIT |
| komdosh/komnet | 100 | MIT |
| maribol/overvibe | 100 | MIT |
| nikicat/claude-tasks | 100 | MIT |
| shenxingy/clade | 100 | MIT |
| xobotyi/cc-foundry | 100 | MIT |
| lauradfarbo/chief-of-staff | 100 | MIT |
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".