sp-tasks

Generates dependency-aware task graphs and tasks.md from spec-kit plan contracts.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/chenziyang110/launchdeck --skill sp-tasks-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-tasks
Source: https://github.com/chenziyang110/launchdeck/tree/main/.claude/skills/sp-tasks
Command: npx skills add https://github.com/chenziyang110/launchdeck --skill sp-tasks-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a finished implementation plan into executable work is error-prone: tasks get misordered, parallel work collides on shared files, and planning obligations silently drop. This Skill compiles a ready plan contract into a validated, dependency-safe task graph with guardrails, parallel batches, and join points before any code is written. ## Core Features & Use Cases - Dependency-aware task generation: Reads plan-contract.json and produces a canonical task-index.json plus a rendered tasks.md with ordered tasks, [P] parallel markers, user-story labels, and explicit join points. - Obligation and scope preservation: Maps every CA-### consequence obligation, MP-* must-preserve item, capability operation, and user-observable UI/CLI/API path to concrete tasks or explicit deferrals. - Adaptive execution modes: Selects light, standard, or heavy modes with native subagent delegation for isolated decomposition lanes, plus deterministic graph validation for cycles, write-set safety, and acceptance coverage. - Use Case: After running /sp-plan on a feature, invoke this Skill to produce a parallel-safe tasks.md organized by user story, then hand off cleanly to /sp-implement for just-in-time worker packet compilation. ## Quick Start Ask the agent to run /sp-tasks on the current feature to generate the dependency-ordered tasks.md and task-index.json from the existing plan contract.

Frequently Asked Questions about sp-tasks

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

FAQPage Schema
How do I generate a tasks.md from a spec-kit plan?▼

Invoke /sp-tasks after the plan phase completes. It reads plan-contract.json, validates the plan revision and scope, then writes a canonical task-index.json and rendered tasks.md with dependency ordering, parallel batches, and join points.

How do I mark tasks as parallelizable in a task graph?▼

Add a [P] marker to tasks with isolated write sets, no dependencies on incomplete tasks, stable upstream inputs, and independent verification. Every parallel batch must be followed by an explicit join point with a validation command and pass condition.

Does sp-tasks work without a spec-kit project structure?▼

No. The Skill requires a spec-kit project with a .specify directory and an existing plan contract. It resolves the feature directory through spec-kit lane commands and refuses to proceed when planning truth is missing or invalid.

Can sp-tasks edit source code or tests during task generation?▼

No. Task generation is artifact-only: it owns the task graph, tasks.md, and task-generation evidence. Source, test, migration, and runtime configuration changes are forbidden and begin only in a separately invoked /sp-implement workflow.

What happens when a plan defect is found during task generation?▼

Task-layer defects like dependency or granularity issues are repaired locally. Defects in requirements, architecture, feasibility, or confirmed scope are routed back to the owning upstream phase such as /sp-plan or /sp-clarify with the specific obligation named.