speckit-tasks

Generate a phased tasks.md from plan.md, spec.md, data-model.md, and contracts.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/vZulin/overlay-clock-timer --skill speckit-tasks-vzulin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/vZulin/overlay-clock-timer/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/vZulin/overlay-clock-timer --skill speckit-tasks-vzulin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate fragmented design artifacts into a single executable tasks.md that prescribes concrete steps, dependencies, and phased organization for feature development.

Core Features & Use Cases

  • Automated tasks generation from plan.md, spec.md, data-model.md, and contracts to produce a centralized tasks document.
  • Multi-phase structure (Phase 1 Setup, Phase 2 Foundational, Phase 3+ per user story, Final Phase) with clear goals and independent test criteria.
  • Dependency graph showing user story completion order and parallel execution opportunities.
  • Template-driven output using .specify/templates/tasks-template.md to ensure consistent checklist formatting and explicit file paths.
  • Extension hooks support (pre- and post-task) via .specify/extensions.yml for automated customization.
  • Validation and reporting: totals by story, MVP scope, and format conformance.
  • Checks for shared infrastructure and cross-cutting concerns to accelerate delivery.

Quick Start

Provide a complete tasks.md by analyzing plan.md, spec.md, data-model.md, and contracts, then structure it into phases and user stories per the project's template.

Frequently Asked Questions about speckit-tasks

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

FAQPage Schema
How do I generate actionable tasks from design artifacts like spec.md and plan.md?▼

To generate actionable tasks from design artifacts, you need a SPEC-like repository layout containing plan.md, spec.md, data-model.md, and contracts. The skill translates these fragmented files into a centralized tasks.md that encodes concrete steps and dependencies for feature development.

What is a dependency-ordered tasks.md file for user stories?▼

A dependency-ordered tasks.md file organizes feature development into a multi-phase structure, aligning tasks by priority user stories. It includes a dependency graph showing completion order and parallel execution opportunities to guide the entire development workflow.

How do I structure development tasks into phases with independent test criteria?▼

You can structure development tasks into phases by using a template-driven approach. The generated tasks.md organizes work into Phase 1 Setup, Phase 2 Foundational, Phase 3+ per user story, and a Final Phase, each with clear goals and independent test criteria.

Do I need a specific repository layout to generate a tasks.md from specifications?▼

Yes, generating a tasks.md requires a SPEC-like repository layout. You must configure extension hooks at .specify/extensions.yml and place output templates at .specify/templates/tasks-template.md to ensure consistent checklist formatting and validation.

Can I customize task generation with extension hooks for my development workflow?▼

Yes, you can customize task generation using extension hooks. The system supports pre- and post-task hooks configured within the .specify/extensions.yml file, enabling automated customization of the generated task set and validation reporting.

What is the best way to visualize user story dependencies and parallel execution opportunities?▼

The best way to visualize user story dependencies is by generating a tasks.md file from your specifications. The output includes a dependency graph showing exact user story completion order and highlighting parallel execution opportunities to accelerate delivery.