speckit-tasks

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

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

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 is specific enough to execute without extra context. ## 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. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallelization marker, story label, and exact file path. - Dependency & Parallelism Mapping: Produces a dependency graph of story completion order and parallel execution examples per story. - Extension Hooks: Supports optional and mandatory pre/post hooks declared in .specify/extensions.yml. - Use Case: After running spec-kit's specify and plan steps for a new feature, invoke this Skill to generate a tasks.md that an LLM or developer can execute incrementally, starting with an MVP scope of just User Story 1. ## Quick Start Ask the agent to generate the tasks.md for the current feature, optionally adding constraints such as including test tasks for a TDD approach.

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 spec-kit feature specification?▼

Run the speckit-tasks skill inside a project with a .specify directory. It reads spec.md and plan.md from the feature directory, then writes a tasks.md organized by user story with sequential task IDs, file paths, and dependency ordering.

What documents does spec-kit task generation require?▼

It requires plan.md for tech stack and structure, and spec.md for prioritized user stories. Optional inputs include data-model.md, contracts/, research.md, quickstart.md, and a constitution.md for project principles.

Does the tasks.md include test tasks by default?▼

No. Test tasks 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.

What format must each generated task follow?▼

Each task must be a markdown checkbox with a sequential ID like T001, an optional [P] parallel marker, a story label like [US1] for story-phase tasks, and a description ending with an exact file path.

Can I run custom hooks before or after task generation?▼

Yes. Hooks declared under hooks.before_tasks and hooks.after_tasks in .specify/extensions.yml are executed or offered based on their optional flag. Hooks with enabled set to false are skipped, and conditions are left to the HookExecutor.

When is speckit-tasks not the right tool?▼

It only works in projects using the spec-kit structure with a .specify directory and prepared design artifacts. For ad-hoc task lists without spec.md and plan.md, a general planning prompt is more appropriate.