speckit-tasks

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

32|9|Updated Feb 2, 2024
One-click install
npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-tasks-esri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/Esri/arcgis-gitops/tree/main/.github/skills/speckit-tasks
Command: npx skills add https://github.com/Esri/arcgis-gitops --skill speckit-tasks-esri

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 and parallelization opportunities. ## Core Features & Use Cases - Story-Organized Task Generation: Reads spec.md, plan.md, data-model.md, and contracts to produce tasks grouped by user story priority (P1, P2, P3). - Strict Checklist Format: Every task follows a validated format with checkbox, task ID, parallel marker, story label, and exact file path. - Extension Hooks: Supports pre- and post-execution hooks defined in .specify/extensions.yml for custom workflow integration. - Use Case: After writing a feature spec and implementation plan with spec-kit, run this Skill to produce a tasks.md where each user story is an independently testable phase, complete with an MVP scope recommendation and dependency graph. ## 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 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 from the feature directory and outputs a tasks.md with phases organized by user story priority.

What files does spec-kit task generation require?

It requires spec.md with prioritized user stories and plan.md with the tech stack and structure. Optional inputs include data-model.md, contracts/, research.md, and quickstart.md, which enrich the generated tasks when present.

Does the tasks generator work without a .specify directory?

No, it requires a spec-kit project structure with a .specify directory containing the setup scripts and feature folders. Without it, the setup-tasks.ps1 script cannot resolve the feature directory and template.

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, and a final Polish phase. Each task has a checkbox, sequential ID, optional [P] parallel marker, story label like [US1], and an exact file path.

Are test tasks always included in the generated task list?

No, test tasks are optional and only generated when explicitly requested in the feature specification or when the user asks for a TDD approach. Implementation tasks are always generated per user story.