task-from-spec

Parse spec.md and metadata.json to generate scored task states with dependencies.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/qazuor/claude-code-plugins --skill task-from-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-from-spec
Source: https://github.com/qazuor/claude-code-plugins/tree/main/plugins/task-master/skills/task-from-spec
Command: npx skills add https://github.com/qazuor/claude-code-plugins --skill task-from-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate end-to-end task generation from approved spec documents, producing a complete, scored, dependency-validated, and phase-organized task state.

Core Features & Use Cases

  • Orchestrates spec-to-task workflows by coordinating the task-atomizer, complexity-scorer, and dependency-grapher to surface a ready-to-run state.
  • Generates ultra-granular tasks with clear ownership, test requirements, and phase-aligned grouping for setup, core, integration, testing, and docs.
  • Produces artifacts including state.json, TODOs.md, and updated index.json for project-wide tracking.

Quick Start

Parse an approved spec and its metadata to generate a complete, ready-to-execute task state with granular tasks, a dependency graph, and a state.json.

Frequently Asked Questions about task-from-spec

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

FAQPage Schema
How do I generate tasks from a spec document?

Generate tasks from a spec document by parsing an approved spec.md and metadata.json file to produce a complete, scored, and dependency-validated task state. The process outputs state.json, TODOs.md, and an updated index for project tracking.

What is spec-to-task workflow automation?

Spec-to-task workflow automation translates approved specifications and acceptance criteria into granular, executable tasks. It coordinates task atomization, complexity scoring, and dependency graphing to organize phases for setup, core, integration, testing, and documentation.

How do I break down complex user stories into granular tasks?

Break down complex user stories by applying multi-pass decomposition that enforces complexity limits. This process atomizes user stories and acceptance criteria into ultra-granular tasks with clear ownership, test requirements, and phase-aligned grouping.

Can I create a dependency graph from acceptance criteria?

Create a dependency graph from acceptance criteria by extracting requirements from the spec metadata and mapping relationships between tasks. The generated state.json captures these dependencies for phase-organized execution.

What files are needed to start project planning from a spec?

Start project planning from a spec requires an approved spec.md document and a metadata.json file. These inputs provide the user stories and acceptance criteria needed to generate the complete task state.

Why do my generated project tasks exceed complexity limits?

Generated project tasks exceed complexity limits when initial decomposition fails to break down large tasks. The system applies multi-pass decomposition to enforce complexity limits, ensuring each task remains granular and executable.