speckit-tasks

Generate a dependency-ordered tasks.md from plan.md and spec.md.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Congtrinhh/sholy-be --skill speckit-tasks-congtrinhh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/Congtrinhh/sholy-be/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/Congtrinhh/sholy-be --skill speckit-tasks-congtrinhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns existing design artifacts (plan.md and spec.md) into an actionable tasks.md that an LLM can complete immediately, including dependencies and per-story independent test criteria.

Core Features & Use Cases

  • Actionable tasks.md generation: Produces a dependency-ordered tasks file using the repo’s tasks template and the feature name from plan.md.
  • Story-first organization: Creates one phase per user story in priority order (P1, P2, P3, etc.), with clear file paths and a strict checklist format.
  • Optional extension hook integration: Reads .specify/extensions.yml (before_tasks/after_tasks) to emit the required hook commands without evaluating hook conditions.

Quick Start

Run the AI with the speckit-tasks skill to generate tasks.md from your repo’s .specify feature directory using your plan.md and spec.md as inputs.

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 dependency-ordered tasks.md from user stories and design artifacts?

You can generate a tasks.md by feeding your plan.md and spec.md design artifacts into the skill. It produces a dependency-ordered file structured by user story priority, complete with file paths and independent test criteria for immediate execution.

How does spec-kit organize implementation phases for multiple user stories?

Spec-kit organizes implementation by creating one phase per user story in strict priority order like P1, P2, and P3. This story-first structure ensures foundational setup tasks precede story-specific implementation, enabling parallel execution where dependencies allow.

Can I integrate custom extension hooks into my generated tasks.md file?

Yes, you can integrate custom extension hooks into your tasks.md file. The skill reads the .specify/extensions.yml configuration to emit required before_tasks and after_tasks hook commands directly into the generated tasks checklist without evaluating hook conditions.

Do I need existing design artifacts before generating a tasks.md?

Yes, you need existing design artifacts. The skill requires a spec-kit project structure containing plan.md and spec.md files as inputs to accurately generate the actionable, dependency-ordered tasks.md with per-story independent test criteria.

What is the best way to structure tasks for parallel execution in a spec-kit project?

The best way to structure tasks for parallel execution is using a generated tasks.md that applies a dependency graph to identify independent test criteria. It groups tasks into setup, foundational, and per-user-story phases to maximize parallel work opportunities.