speckit-tasks

Generate dependency-ordered tasks.md checklists from spec-kit design artifacts.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Powerworks/Underwriting --skill speckit-tasks-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/Powerworks/Underwriting/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/Powerworks/Underwriting --skill speckit-tasks-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a feature specification and implementation plan into an actionable, ordered task list is tedious and error-prone. This Skill automates that step by reading your spec-kit design documents and producing a structured tasks.md where every task has an ID, file path, and story label. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md user stories with priorities and creates one phase per story, plus Setup, Foundational, and Polish phases. - Dependency & Parallelism Mapping: Produces a dependency graph of story completion order and marks parallelizable tasks with [P] labels. - Extension Hook Support: Executes pre- and post-generation hooks defined in .specify/extensions.yml for workflow customization. - Use Case: After running speckit-plan for a new feature, invoke this Skill to generate a tasks.md where each user story is an independently testable increment, then hand it to an LLM or developer for execution. ## Quick Start Ask the assistant to generate the tasks.md for the current feature based on the spec and plan in the .specify 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, organizes tasks by user story priority, and writes a tasks.md with checkbox-formatted tasks including IDs, story labels, and file paths.

What is the task checklist format in spec-kit tasks.md?▼

Every task follows the format '- [ ] [TaskID] [P?] [Story?] Description with file path'. The [P] marker indicates parallelizable tasks, and [US1], [US2] labels map tasks to user stories from spec.md. Setup, Foundational, and Polish phases have no story label.

Does speckit-tasks require a spec-kit project structure?▼

Yes, it requires a .specify directory with the setup-tasks.sh script and design documents like plan.md and spec.md in the feature directory. Optional documents such as data-model.md, contracts/, and research.md enrich the generated tasks when present.

Are test tasks always generated in tasks.md?▼

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. Otherwise the output focuses on implementation tasks organized by user story.

How do extension hooks work with task generation?▼

If .specify/extensions.yml defines hooks under before_tasks or after_tasks, the skill evaluates them before and after generation. Mandatory hooks are executed automatically, while optional hooks are presented for the user to invoke manually.