speckit.tasks

Generate a dependency-ordered tasks document from Speckit design artifacts.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.tasks
Source: https://github.com/lofidonut3/oh-my-speckit/tree/main/skills/speckit.tasks
Command: npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates an actionable, dependency-ordered tasks document for a feature using available design artifacts, enabling a clear path from plan to implementation.

Core Features & Use Cases

  • Automated task decomposition: Breaks down a feature into concrete, executable tasks organized by user stories.
  • Speckit workflow integration: Designed to run after /speckit.plan and to feed downstream steps like /speckit.analyze or /speckit.implement.
  • Traceability: Links tasks to plan/spec inputs and includes per-task IDs and skill tags for auditability.

Quick Start

Use the speckit.tasks skill to generate tasks from your current Speckit artifacts.

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?

Generate actionable tasks from design artifacts by reading inputs from specs and plans directories to produce a structured, dependency-ordered tasks document with user stories and IDs.

How do I break down a feature into executable tasks organized by user stories?

Break down a feature into executable tasks by applying automated task decomposition to available design artifacts, outputting organized user stories with mandatory skill tags for auditability.

Do I need to run the speckit.plan phase before generating a tasks document?

Yes, you need to run the speckit.plan phase first. The task generation applies after planning to break down implementation into executable tasks and prepare them for downstream steps.

What design artifact directories are read during automated task decomposition?

Automated task decomposition reads design artifacts from the .github/speckit/specs, .opencode/plans, and .opencode/designs directories to generate the final structured tasks file.

How does dependency-ordered task generation feed into downstream implementation?

Dependency-ordered task generation feeds downstream implementation by preparing a structured tasks file designed to run before downstream steps like speckit.analyze or speckit.implement.

Can I trace generated tasks back to their original plan and spec inputs?

Yes, you can trace generated tasks back to original plan and spec inputs. The output links tasks to their inputs and includes per-task IDs and mandatory skill tags for full auditability.