speckit-tasks

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

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/gkuga/monit-rs --skill speckit-tasks-gkuga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/gkuga/monit-rs/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/gkuga/monit-rs --skill speckit-tasks-gkuga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning feature specifications and design documents into an actionable, ordered implementation plan is time-consuming and error-prone. This Skill automates the creation of a structured tasks.md file so every user story becomes a set of concrete, independently testable tasks. ## 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. - Strict Checklist Format: Every task follows a validated format with checkbox, sequential task ID, parallelization marker, story label, and exact file path. - Dependency & Parallelism Analysis: Outputs a dependency graph of story completion order plus parallel execution examples and a suggested MVP scope. - Extension Hooks: Supports optional and mandatory pre/post hooks defined in .specify/extensions.yml. - Use Case: After writing a feature spec and implementation plan with spec-kit, run this Skill to instantly produce a tasks.md that an LLM or developer can execute task-by-task without extra context. ## Quick Start Ask the AI 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 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.

How are tasks organized in the generated tasks.md?

Tasks are grouped into phases: Setup, Foundational prerequisites, one phase per user story in priority order (P1, P2, P3), and a final Polish phase. Each user story phase is independently testable and includes models, services, and endpoints for that story.

What project structure does spec-kit task generation require?

It requires a spec-kit project with a .specify directory containing scripts like check-prerequisites.sh and templates like tasks-template.md. The feature directory must contain at least spec.md and plan.md; data-model.md, contracts, and research.md are optional.

Does the task generator create test tasks automatically?

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, in which case contract tests are placed before implementation tasks.

What is the task checklist format used in tasks.md?

Every task uses the format '- [ ] [TaskID] [P?] [Story?] Description with file path'. The [P] marker indicates parallelizable tasks, and story labels like [US1] are required only for user story phase tasks.