create-tasks

Break a specification into implementable tasks. Use after spec.md is complete to create tasks.md with grouped, ordered, dependency-aware task breakdown.

⭐2stars🔀0forks📁View on GitHub🕐Updated Dec 18, 2025

When & Why to Use This Skill

This Claude skill automates the transition from software specifications to actionable implementation plans. It analyzes technical requirements to generate a structured, dependency-aware task list (tasks.md), organizing work by specialization—such as database, API, and frontend—to ensure a clear and efficient path from design to code.

Use Cases

  • Technical Planning: Automatically breaking down complex feature specifications into granular, implementable tasks with clear dependency mapping to prevent development bottlenecks.
  • Workflow Automation: Seamlessly syncing planned task groups with internal todo systems using tools like todo_write to track implementation progress and maintain project momentum.
  • Test-Driven Development: Defining focused test cases for each task group during the planning phase to ensure high code quality and verification throughout the implementation lifecycle.
namecreate-tasks
descriptionBreak a specification into implementable tasks. Use after spec.md is complete to create tasks.md with grouped, ordered, dependency-aware task breakdown.

Create Tasks

Break a specification into a structured, implementable task list.

When to Use

  • spec.md is complete and verified
  • Ready to plan implementation work
  • Need clear task breakdown with dependencies

Workflow

  1. Analyze Spec

    • Read amp-os/specs/[feature]/spec.md
    • Read amp-os/specs/[feature]/planning/requirements.md
  2. Plan Task Groups

    • Group by specialization (database, API, frontend, testing)
    • Order by dependencies
    • Include 2-8 focused tests per group
  3. Create Tasks Document

  4. Sync with Amp Todo System

    • Use todo_write to create todos for each task group
    • Tag with spec:[feature-name], phase:implementation

Task Structure

Each task group should have:

  • Clear dependencies
  • 2-8 focused tests (written first)
  • Implementation sub-tasks
  • Test verification (run only group tests)
  • Acceptance criteria

Resources

Amp Tools to Use

  • todo_write - Sync tasks to Amp's todo system
  • todo_read - Check existing task status