speckit.tasks

Generate dependency-ordered task checklists from plan.md and spec.md.

Updated Oct 4, 2025
One-click install
npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-tasks-peancharoen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit.tasks
Source: https://github.com/peancharoen/lcbp3/tree/main/.agents/skills/speckit.tasks
Command: npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-tasks-peancharoen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill turns scattered design artifacts (plan.md, spec.md, data-models, and contracts) into a single, actionable, dependency-ordered tasks.md so teams can implement features incrementally and test each user story independently.

Core Features & Use Cases

  • Design artifact ingestion: Reads plan.md and spec.md and optionally data-model.md, contracts/, research.md and quickstart.md to extract tech stack, user stories, entities, and endpoints.
  • Checklist task generation: Produces atomic, checklist-formatted tasks with sequential IDs, story labels, file paths, and dependency information suitable for LLM execution or developer handoff.
  • Execution planning: Emits dependency graphs, parallel execution suggestions, phase-based structure (Setup → Foundational → User Stories → Polish), and an implementation strategy for MVP-first delivery.
  • Use Case: Convert a feature folder containing plan.md and spec.md into an immediately executable tasks.md that contains per-story test criteria, implementation steps, and parallelization guidance.

Quick Start

Use the speckit.tasks skill with the repository context and feature arguments to generate a complete tasks.md for the target FEATURE_DIR.

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 feature design artifacts?▼

Checklist task generation creates atomic tasks formatted with sequential IDs, story labels, file paths, and dependency information, ensuring each task is structured for immediate execution or developer handoff.

How do I structure executable tasks for incremental feature implementation?▼

The skill optionally invokes repository helper scripts to discover the FEATURE_DIR, automatically locating the target folder containing your plan.md, spec.md, and optional data-model.md or contracts for ingestion.

What design artifacts do I need to generate an actionable tasks.md file?▼

Optional artifacts like data-model.md and contracts provide entities and endpoints that enrich the task generation process, allowing the skill to include specific file paths and validation criteria in the output.

Can I use dependency graphs to suggest parallel execution for user stories?▼

Parallelization guidance identifies independent tasks within the dependency graph, suggesting concurrent execution paths to accelerate MVP-first delivery while maintaining required implementation order.

When do I need to parse spec.md and plan.md into a checklist format?▼

Checklist-formatted tasks provide the structured, sequential format necessary for automated execution systems or developers to systematically track and validate each implementation step against defined criteria.