speckit-tasks-graph

Generates tasks.md with graphify-verified parallel markers and a machine-readable execution waves DAG.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-tasks-graph-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks-graph
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/speckit-tasks-graph
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-tasks-graph-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Spec Kit's stock task generation marks tasks as parallelizable based on LLM guesses, which can schedule conflicting edits to the same files in parallel and produce broken implementations. This Skill grounds parallel markers in a real dependency graph of the codebase and emits a machine-readable wave plan that a parallel implementer can execute directly. ## Core Features & Use Cases - Graph-verified [P] markers: Uses graphify dependency edges and shared/mutable file lists to confirm or strip parallel markers instead of relying on heuristics. - Execution Waves DAG: Appends a topologically-ordered, machine-readable ## Execution Waves section to tasks.md that /speckit-implement-parallel consumes, packed by greedy earliest-admission to minimize wave count. - Session-sized task merging: Merges structurally dependent tasks (depth capped at 2, never across phase barriers) so each dispatched agent session gets a right-sized unit of work. - Use Case: After running spec-kit plan on a multi-story feature, invoke this Skill to produce a tasks.md where parallel waves are provably conflict-free, then hand it to /speckit-implement-parallel for concurrent agent execution. ## Quick Start Ask the assistant to generate the task list for the current feature using graph-aware parallel markers and an execution waves plan instead of the stock speckit-tasks output.

Frequently Asked Questions about speckit-tasks-graph

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

FAQPage Schema
How do I generate parallel-safe tasks from a spec-kit plan?

Run this Skill in place of /speckit-tasks after planning. It generates the standard tasks.md, annotates every task with files, deps, and mutates fields, verifies [P] markers against graphify dependency edges, and appends an Execution Waves section for parallel implementation.

What is the difference between speckit-tasks and speckit-tasks-graph?

speckit-tasks-graph produces the same tasks.md format as speckit-tasks but adds graphify-verified [P] markers and a machine-readable Execution Waves DAG. The stock command marks parallelism heuristically, while this variant derives it from real import and call edges.

Does speckit-tasks-graph work without a graphify dependency graph?

Yes, it falls back to the stock heuristic of different files plus no stated dependency when graphify-out/graph.json is absent. The degradation is noted in the completion report so you know the parallel markers were not graph-verified.

Why are some tasks merged before wave planning?

Tasks whose only dependency is a single predecessor and whose mutated files are disjoint from all other tasks are merged so each dispatched agent session gets a right-sized unit of work. Merge chains are capped at depth 2 and never cross Setup or Foundational phase barriers.

What happens when two parallel tasks edit the same file?

They are never co-scheduled. The wave admission rule requires pairwise-disjoint mutable-file sets, so tasks touching shared files are pinned to serial waves, and the shared-file serialization is documented in the Execution Waves section.