speckit-tasks

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

4|Updated May 16, 2025
One-click install
npx skills add https://github.com/AustinZ21/EggHatch-AI --skill speckit-tasks-austinz21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/AustinZ21/EggHatch-AI/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/AustinZ21/EggHatch-AI --skill speckit-tasks-austinz21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating structured, dependency-ordered task lists for feature development from scattered design artifacts is time-consuming, inconsistent, and often misses critical dependencies or misaligns with user story priorities. This Skill automates the entire process to deliver production-ready task breakdowns in seconds.

Core Features & Use Cases

  • Automated Design Artifact Parsing: Reads standard spec-kit project documents (plan.md, spec.md, data-model.md, interface contracts, and research notes) to extract tech stack details, user story priorities, and entity relationships.
  • Dependency-Aware Task Organization: Groups tasks by user story priority, maps cross-story dependencies, and identifies parallel execution opportunities to streamline development workflows.
  • Use Case: A product engineering team building a new payment processing feature can use this Skill to automatically generate a complete tasks.md file that includes setup steps, foundational prerequisites, per-user-story implementation tasks, independent test criteria, and a clear MVP scope, eliminating hours of manual planning work.

Quick Start

Generate a complete, executable tasks.md file for my current feature using the available design documents 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 task list from a feature spec automatically?▼

Generating a task list from a feature spec is automated by parsing structured design artifacts in a .specify directory, extracting user story priorities and dependencies, and outputting a standardized, executable tasks.md file with sequential IDs and parallel execution markers.

How does dependency mapping work for agile feature planning?▼

Dependency mapping for agile feature planning works by reading spec-kit documents like data-model.md and interface contracts, grouping tasks by user story priority, and identifying cross-story dependencies to flag parallel execution opportunities for development teams.

Do I need a spec-kit formatted project to create dependency-ordered task lists?▼

Yes, you need a spec-kit formatted project with a .specify directory containing plan.md and spec.md files, along with optional supporting design documents like data-model.md and research notes, to automatically generate standardized, dependency-ordered task breakdowns.

What's the best way to break down software features into executable tasks for AI coding assistants?▼

The best way to break down software features for AI coding assistants is generating a tasks.md file with sequential task IDs, explicit file paths, and user story labels, enabling immediate, context-free implementation without manual planning work.

Can I parse interface contracts and data models to identify parallel execution opportunities?▼

Yes, you can parse interface contracts and data-model.md documents from your .specify directory to map entity relationships, identify cross-story dependencies, and automatically mark parallel execution opportunities in the generated task list.

Why do manually created task lists miss critical dependencies during feature development?▼

Manually created task lists miss critical dependencies because scattered design artifacts make it difficult to consistently map cross-story relationships and align tasks with user story priorities, a problem solved by automated dependency-aware task organization.