sdd-generate-tasks

Generates a tasks.md DAG of atomic tasks for an SDD feature from approved spec and plan files.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/phm-aguiar/test_documentacao --skill sdd-generate-tasks-phm-aguiar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-generate-tasks
Source: https://github.com/phm-aguiar/test_documentacao/tree/main/.claude/skills/sdd-generate-tasks
Command: npx skills add https://github.com/phm-aguiar/test_documentacao --skill sdd-generate-tasks-phm-aguiar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Turning an approved specification and implementation plan into an executable, dependency-aware task breakdown is error-prone: tasks get grouped together, parallel work conflicts over shared files, and failure scenarios are forgotten. This Skill produces a validated tasks.md containing a Directed Acyclic Graph (DAG) of atomic tasks with roles, dependencies, parallelism flags, and file ownership. ## Core Features & Use Cases - DAG task generation: Derives atomic tasks (Tnnn) from spec.md, plan.md, and discovery reports, each with Papel (researcher/analyst/executor), Dependências, Paralelizável, Arquivos, and Wiki-Keywords fields. - Approval gate and validation: Aborts unless spec.md has Aprovado: true, then validates the DAG for cycles, broken dependencies, orphan tasks, and file conflicts between parallel tasks. - Phase-by-phase interaction: Proposes tasks one phase at a time with user approval before continuing, and supports LATTE coordination graphs (graph-operators, heartbeats, agent assignments) plus optional --with-memory experiential hints. - Use Case: After approving a feature spec and plan, ask the assistant to generate the execution matrix; it produces a tasks.md where Gherkin success and failure scenarios each map to separate executor tasks with disjoint file sets. ## Quick Start Generate the tasks.md execution matrix for the feature in specs/features/004-chat using the approved spec and plan.

Frequently Asked Questions about sdd-generate-tasks

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

FAQPage Schema
How do I generate a tasks.md task breakdown from a spec?▼

Run the skill with the feature directory path, for example specs/features/<id>-<slug>. It reads spec.md and plan.md, derives atomic tasks with dependencies and parallelism flags, and writes a validated tasks.md after phase-by-phase approval.

What is a task DAG in spec-driven development?▼

A task DAG is a Directed Acyclic Graph where each task (Tnnn) declares its dependencies, role, parallelizability, and files. It lets executors run independent tasks in parallel while guaranteeing dependent tasks wait for prerequisites to complete.

Why does task generation abort with an approval gate error?▼

The skill enforces a hard gate: spec.md must contain Aprovado: true before tasks are generated. If the spec is unapproved, generation aborts so the execution matrix is never built on an unreviewed specification.

Can parallel tasks modify the same file?▼

No. Tasks marked Paralelizável: true must have disjoint file sets; if two tasks share a path, the skill forces them sequential and adds an explicit dependency. An exception exists for different extensions like .feature and .go in the same directory.

What is LATTE mode in tasks.md?▼

LATTE mode activates when graph-operators: enabled is set in the tasks.md frontmatter. It adds heartbeat-threshold and max-rounds settings, per-task agent assignments, depends_on lists, and a Coordination Graph section for dynamic multi-worker execution.

When should I not use this task generation skill?▼

Skip it when no approved spec.md and plan.md exist, since the approval gate will abort. It is also unnecessary for trivial single-step changes where a full DAG with phases, roles, and validation adds overhead without benefit.