speckit-tasks

Name: speckit-tasks
Availability: InStock
Author: Ahmed

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

Updated Sep 24, 2025

Search Tags:#automation #workflow #planning #tasks #speckit #spec-kit

Ready to run

npx skills add https://github.com/AhmedHassaan-7OS/money_follow --skill speckit-tasks-ahmedhassaan-7os

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/AhmedHassaan-7OS/money_follow/tree/main/project_disc/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/AhmedHassaan-7OS/money_follow --skill speckit-tasks-ahmedhassaan-7os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a structured, dependency-ordered tasks.md from design artifacts to accelerate feature implementation and align teams with plan artifacts.

Core Features & Use Cases

Converts plan.md and spec.md into a phased task breakdown organized by user stories (US1, US2, US3) with explicit task IDs.
Generates a dependency graph and clear phase sequencing (Setup, Foundational, US phases, Polish) to enable parallel execution where possible.
Reads optional design artifacts (data-model.md, contracts/, research.md) to enrich tasks and traceability.

Quick Start

Provide a feature's design artifacts under a .specify directory and run the speckit-tasks skill to generate tasks.md.

Frequently Asked Questions about speckit-tasks

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

FAQPage Schema

How do I turn design specs into an actionable task plan?▼

To turn design specs into an actionable task plan, you provide feature artifacts like plan.md and spec.md under a .specify directory. The tool reads these inputs and generates a dependency-ordered tasks.md document structured for phased execution.

How do I generate a dependency-ordered task list from a spec.md file?▼

Generating a dependency-ordered task list from spec.md requires placing the file in a .specify directory. The system maps the design artifacts into a phased workflow with explicit task IDs and outputs a checklist-formatted tasks document.

What is the best way to structure feature implementation tasks from a spec-kit?▼

The best way to structure feature implementation tasks from a spec-kit is mapping them into Setup, Foundational, User Story, and Polish phases. This dependency-ordered structure enables parallel execution where possible and aligns teams with plan artifacts.

Do I need a .specify directory to generate a phased task workflow?▼

Yes, you need a .specify directory structure to generate a phased task workflow. The system validates prerequisites by reading plan.md and spec.md from this directory, along with optional artifacts like data-model.md and contracts, to build the executable task outline.

Can I use optional design artifacts like data-model.md to enrich generated tasks?▼

Yes, you can use optional design artifacts like data-model.md, research.md, and files in a contracts directory to enrich generated tasks. The system reads these alongside plan.md to enhance task traceability and provide deeper context for feature implementation.

Why are my generated tasks organized into Setup and Foundational phases?▼

Generated tasks are organized into Setup and Foundational phases to build a dependency graph and ensure proper sequencing. This structure validates prerequisites first, enabling parallel execution of user story phases later in the implementation workflow.