Tasks

Generates TDD-ordered task breakdowns with sequential IDs from implementation plans and writes them to tasks.md files.

17|7|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/rsts-dev/claude-buddy-marketplace --skill tasks-rsts-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Tasks
Source: https://github.com/rsts-dev/claude-buddy-marketplace/tree/main/plugins/buddy/skills/Tasks
Command: npx skills add https://github.com/rsts-dev/claude-buddy-marketplace --skill tasks-rsts-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Generate TDD-ordered tasks from implementation plans
  • Mark parallel tasks with [P] and track dependencies
  • Write results to specs/[YYYYMMDD-slug]/tasks.md

Quick Start

Provide a plan in specs/ and run the task generator to produce specs/[slug]/tasks.md with sequential IDs.

Frequently Asked Questions about Tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate TDD-ordered tasks from an implementation plan?

Yes, this task generator marks parallel tasks with [P] and tracks dependencies automatically, writing the structured results to specs/[slug]/tasks.md for your implementation workflow.

Do I need existing specs and design documents to automate task breakdown?

The task generator enforces tests-before-implementation by applying domain-aware templates, structuring your workflow so that test creation logically precedes implementation steps in the generated tasks.

What's the best way to structure implementation plans for parallel task generation?

Generated tasks are written to specs/[YYYYMMDD-slug]/tasks.md, providing a structured file with sequential IDs and dependency tracking to guide your tests-before-implementation workflow.

Can I use this automated task generator across different project domains?

You should not use this approach if your project lacks specs or design documents, as the generator requires these implementation plans to produce structured, TDD-ordered task breakdowns.