speckit-tasks

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

Updated Dec 5, 2025
One-click install
npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-tasks-apothecaryman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/ApothecaryMan/pharmaflow-ai/tree/main/.agent/skills/speckit-tasks
Command: npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill speckit-tasks-apothecaryman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires spec-kit, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of a comprehensive, task-ordered tasks.md file for feature development, saving time and reducing manual errors in spec-kit projects.

Core Features & Use Cases

  • Task Generation: Automatically generates a tasks.md file with dependency-ordered tasks based on design artifacts.
  • Compatibility: Designed for spec-kit project structures with a .specify/ directory.
  • Use Case: When starting a new feature, use this Skill to create a detailed tasks.md that outlines the development process, including setup, foundational tasks, and user story-specific phases.

Quick Start

Run the 'speckit-tasks' skill to generate a tasks.md for your feature.

Frequently Asked Questions about speckit-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate task generation for spec-kit feature development?

Automating task generation for spec-kit feature development involves parsing design artifacts to produce a dependency-ordered tasks.md file. This process requires a spec-kit project structure with a .specify/ directory to map out development phases automatically.

What design artifacts are needed to generate a dependency-ordered tasks.md file?

Generating a dependency-ordered tasks.md file requires plan.md, spec.md, data-model.md, and contracts/ design artifacts. The Skill analyzes these inputs from your .specify/ directory to outline the development process including foundational tasks and user story phases.

Can I use this task generation Skill without a .specify/ directory?

No, you cannot use this task generation Skill without a .specify/ directory. The automation explicitly requires an existing spec-kit project structure containing this directory to parse the necessary design artifacts and generate the tasks.md file.

How does automated task generation handle development phase ordering?

Automated task generation handles development phase ordering by analyzing dependencies within your design artifacts. It creates a structured tasks.md file that sequences setup, foundational tasks, and user story-specific phases based on the parsed relationships.

What's the best way to structure spec-kit projects for automated task generation?

The best way to structure spec-kit projects for automated task generation is to maintain standard design artifacts like plan.md, spec.md, data-model.md, and contracts/ within the .specify/ directory to ensure accurate dependency-ordered task output.