speckit-tasks

Generate dependency-ordered tasks.md from design artifacts like plan.md and spec.md.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/alansmello/Amani_ImportadosERP --skill speckit-tasks-alansmello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/alansmello/Amani_ImportadosERP/tree/main/.cursor/skills/speckit-tasks
Command: npx skills add https://github.com/alansmello/Amani_ImportadosERP --skill speckit-tasks-alansmello

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates actionable, dependency-ordered tasks from available design artifacts to accelerate feature delivery and alignment across teams.

Core Features & Use Cases

  • Artifact-driven planning: Builds a tasks.md organized by feature, phase, and dependencies from plan.md, spec.md, data-model.md, contracts/, and research.md.
  • Execution-ready output: Produces clear file paths, a strict checklist format, and parallelization hints to guide implementation.
  • Collaboration-friendly: Aligns multiple stakeholders by mapping user stories to concrete tasks and milestones.

Quick Start

Provide a tasks.md tailored to the current repository's design artifacts by invoking the speckit-tasks workflow.

Frequently Asked Questions about speckit-tasks

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

FAQPage Schema
How do I generate a dependency-ordered task list from design artifacts?

Generating a dependency-ordered task list involves processing plan.md, spec.md, and contracts/ to map user stories to concrete tasks, establish execution dependencies, and structure delivery phases in an output tasks.md file.

What is artifact-driven planning for feature implementation?

Artifact-driven planning uses existing design documents like research.md and data-model.md to automatically build a structured, phase-based tasks.md with exact file paths and parallelization hints to guide feature implementation.

How do I map user stories to concrete development tasks and milestones?

Mapping user stories to development tasks is done by applying a workflow across spec.md and plan.md files, which aligns multiple stakeholders by translating stories into execution-ready checklists with explicit dependencies.

Do I need spec.md and plan.md files to create an execution-ready task plan?

Creating an execution-ready task plan requires available design artifacts such as plan.md, spec.md, data-model.md, contracts/, and research.md to generate strict checklists and phase-based delivery structures.

What's the best way to structure tasks.md for parallel implementation?

Structuring tasks.md for parallel implementation requires organizing tasks by feature and phase, applying dependency ordering and explicit parallelization notes to guide concurrent development.

Why does my generated task plan lack validation notes and exact file paths?

Your generated task plan lacks validation notes and exact file paths when the workflow cannot fully map dependencies across available design artifacts like spec.md, data-model.md, and contracts/.