speckit-tasks

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

44|10|Updated Mar 28, 2024
One-click install
npx skills add https://github.com/sensein/senselab --skill speckit-tasks-sensein
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/sensein/senselab/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/sensein/senselab --skill speckit-tasks-sensein

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 the creation of a tasks.md file that organizes work by user story with clear dependencies and parallelization opportunities. ## Core Features & Use Cases - Design-Artifact-Driven Generation: Reads plan.md, spec.md, data-model.md, contracts/, research.md, and quickstart.md from a spec-kit project to build tasks grounded in actual design decisions. - User-Story-Organized Phases: Produces Setup, Foundational, per-user-story, and Polish phases, each independently testable, with strict checklist formatting (checkbox, task ID, [P] parallel markers, [US#] story labels, file paths). - Extension Hook Support: Checks .specify/extensions.yml for before_tasks and after_tasks hooks and executes or surfaces them appropriately. - Use Case: After writing a feature spec and implementation plan with spec-kit, invoke this Skill to produce a tasks.md where each task is specific enough for an LLM or developer to execute without additional context, including a suggested MVP scope. ## Quick Start Run the speckit-tasks skill to generate a dependency-ordered tasks.md for the current feature from the available spec-kit design documents.

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 file from a feature specification?

Run this Skill inside a spec-kit project after creating spec.md and plan.md. It reads the design artifacts from the feature directory and writes a tasks.md organized by user story with sequential task IDs, file paths, and dependency ordering.

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

Every task follows the format '- [ ] [TaskID] [P?] [Story?] Description with file path'. The checkbox and sequential ID like T001 are required, [P] marks parallelizable tasks, and [US1]-style story labels are required only for user story phase tasks.

Does speckit-tasks require all design documents to exist?

No. Only plan.md and spec.md are required. Data-model.md, contracts/, research.md, and quickstart.md are optional, and tasks are generated based on whichever documents are available in the feature directory.

Are test tasks always generated in tasks.md?

No. Test tasks are optional and 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 are spec-kit extension hooks in task generation?

Hooks are commands defined in .specify/extensions.yml under hooks.before_tasks or hooks.after_tasks. Mandatory hooks execute automatically before or after generation, while optional hooks are surfaced as suggestions for the user to run.