speckit-tasks

Generates ordered task lists with dependencies from SpecKit design artifacts.

10|3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/raphaelfh/newsweep --skill speckit-tasks-raphaelfh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/raphaelfh/newsweep/tree/main/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/raphaelfh/newsweep --skill speckit-tasks-raphaelfh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill transforms design artifacts (plan.md, spec.md, etc.) into an actionable, dependency-ordered tasks.md to guide feature implementation and ensure traceability.

Core Features & Use Cases

  • Automated task generation: builds a tasks.md organized by setup, foundational work, and user stories (US1, US2, ...).
  • Dependency graph & phased execution: creates phases aligned with the spec.md priorities and shows task dependencies.
  • Hook-aware workflow: respects .specify/extensions.yml hooks before and after task generation.

Quick Start

Place plan.md, spec.md, and optional data-model.md in the project FEATURE_DIR; 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 generate a dependency-ordered tasks.md from design artifacts?

Generating a dependency-ordered tasks.md from design artifacts involves reading plan.md and spec.md files to output a structured task plan organized by user stories and execution phases.

What is a tasks.md file and when do I need one for feature implementation?

A tasks.md file is an actionable checklist that guides feature implementation by breaking work into setup, foundational tasks, and user stories. You need it when transforming project specifications into traceable engineering tasks.

Can I generate user story tasks from a spec.md without a data-model.md file?

Yes, you can generate user story tasks from a spec.md without a data-model.md file. The skill requires plan.md and spec.md to build the dependency graph, while data-model.md, contracts/, and research.md are optional inputs.

How do I structure user stories and phases in a task plan from a spec?

Structuring user stories and phases in a task plan from a spec requires aligning generated tasks with the priorities defined in spec.md. The output organizes work into setup, foundational phases, and user stories (US1, US2) with strict checklist formatting and file paths.

Does task generation work with extension hooks in a spec-kit repository?

Task generation works with extension hooks in a spec-kit repository by validating against configurations defined in .specify/extensions.yml before and after the tasks.md file is created.

What are the limitations of automated task generation from project specifications?

Limitations of automated task generation from project specifications include requiring a strict .specify/spec-kit directory structure, and the output is restricted to the scope of available artifacts like plan.md and spec.md rather than open-ended planning.