speckit-tasks

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-tasks-alidotcom2000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/alidotcom2000/RSSFeedReader/tree/main/.github/skills/speckit-tasks
Command: npx skills add https://github.com/alidotcom2000/RSSFeedReader --skill speckit-tasks-alidotcom2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is manual and error-prone. This Skill automates the creation of a tasks.md file that organizes work by user story with clear dependencies, parallelization markers, and file paths. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md, plan.md, data-model.md, and contracts to produce one phase per user story in priority order, plus setup, foundational, and polish phases. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, [P] parallel markers, [USn] story labels, and exact file paths. - Extension Hook Support: Executes mandatory and optional pre/post hooks defined in .specify/extensions.yml before and after task generation. - Use Case: After writing a feature spec and implementation plan in a spec-kit project, run this Skill to produce a tasks.md where each user story is an independently testable increment with a suggested MVP scope. ## Quick Start Ask the agent to generate the tasks.md for the current feature based on the spec and plan in the .specify feature 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 the speckit-tasks Skill in a spec-kit project after creating spec.md and plan.md. It reads the design artifacts in the feature directory and produces a tasks.md organized by user story with sequential task IDs, dependencies, and file paths.

What documents are required for spec-kit task generation?▼

plan.md and spec.md are required, providing the tech stack and prioritized user stories. Optional documents like data-model.md, contracts/, research.md, and quickstart.md enrich the generated tasks but are not mandatory.

Does speckit-tasks work without a .specify directory?▼

No, it requires the spec-kit project structure with a .specify/ directory. The setup script .specify/scripts/powershell/setup-tasks.ps1 must run to locate the feature directory and tasks template.

How are tasks organized in the generated tasks.md?▼

Tasks are grouped into phases: Setup, Foundational, one phase per user story in priority order, and a final Polish phase. Each task uses a strict checklist format with checkbox, task ID, optional [P] parallel marker, [USn] story label, and file path.

Are test tasks always included in the generated task list?▼

No, test tasks are optional. They are only generated when explicitly requested in the feature specification or when the user asks for a TDD approach.