speckit-tasks

Generates a dependency-ordered tasks.md from spec-kit design artifacts.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-tasks-lluisfont
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/lluisfont/clickup-reporting/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/lluisfont/clickup-reporting --skill speckit-tasks-lluisfont

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is slow and error-prone. This Skill automates the creation of a tasks.md file that organizes work by user story so each increment is independently implementable and testable. ## Core Features & Use Cases - Artifact-Driven Task Generation: Reads plan.md, spec.md, data-model.md, contracts/, research.md, and quickstart.md from a spec-kit feature directory to derive tasks. - User-Story Organization: Produces phases for setup, foundational work, one phase per prioritized user story, and polish, with dependency graphs and parallel execution examples. - Strict Checklist Format: Enforces a consistent task format with checkboxes, sequential task IDs, [P] parallel markers, [USn] story labels, and exact file paths. - Use Case: After writing a spec and plan for a new feature, run this Skill to produce a tasks.md where an LLM or developer can execute each task without additional context, starting from an MVP scope of just User Story 1. ## Quick Start Ask the agent to generate the tasks.md for the current feature using the spec and plan in the spec-kit project directory.

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 tasks.md from a feature specification?

Run this Skill inside a spec-kit project. It executes .specify/scripts/powershell/setup-tasks.ps1 to locate the feature directory, loads spec.md and plan.md, then writes a tasks.md organized by user story with sequential task IDs and file paths.

What is spec-kit task generation by user story?

It is a task organization method where each user story from spec.md gets its own phase containing the models, services, and endpoints it needs. This makes every phase an independently testable increment, with setup and foundational phases preceding all stories.

Does this Skill work without a .specify directory?

No. The Skill requires a spec-kit project structure, including the .specify directory, the setup-tasks.ps1 script, and a tasks template. Without these, the setup step cannot resolve FEATURE_DIR or TASKS_TEMPLATE.

Are test tasks always included in the generated tasks.md?

No. Test tasks are optional and are only generated when explicitly requested in the feature specification or when the user asks for a TDD approach. Otherwise phases contain only implementation tasks.

What format must each generated task follow?

Every task must be a markdown checkbox with a sequential ID like T001, an optional [P] parallel marker, a [USn] story label for user-story phases, and a description ending with an exact file path.