Decompose SDD proposals into dependency-ordered implementation task checklists.
npx skills add https://github.com/aroca89/roca_teams --skill sdd-tasks-aroca89
Please help me install this Agent Skill. Skill: sdd-tasks Source: https://github.com/aroca89/roca_teams/tree/main/skills/sdd-tasks Command: npx skills add https://github.com/aroca89/roca_teams --skill sdd-tasks-aroca89
When an SDD change reaches the orchestration phase, this skill prevents vague implementation steps by turning proposals, specs, and designs into a precise task checklist ready for execution.
Tell the orchestrator to run the sdd-tasks skill to create the implementation task checklist for the active change.
High-intent search queries and answers about installing and using this skill.
To generate implementation tasks from software design specs, you decompose a change proposal into a precise, dependency-ordered checklist. This breakdown reads your proposal, spec, and design artifacts to produce verifiable, test-focused tasks ready for execution.
Task breakdown handles persistence modes like engram, openspec, hybrid, and none by respecting the active strategy during generation. Generated tasks are either stored or returned according to the configured mode, ensuring outputs align with your memory persistence rules.
The best way to organize implementation checklists for SDD readiness is creating a multi-phase tasks.md file. This file uses dependency-ordered, test-focused, verifiable checkboxes that keep your implementation and verification steps aligned with the original spec.
You need an orchestrator to provide the proposal, specs, and design artifacts before creating actionable tasks. The orchestrator supplies full context via a mandated memory search and observation flow, ensuring the task checklist captures all necessary design information.
Dependency-ordered checklists are important for spec-driven development because they prevent vague implementation steps by enforcing a logical sequence. This ordering ensures tasks honor persistence rules and highlights required testing steps, keeping verification aligned with the spec.
You cannot use this task decomposition approach without prior design artifacts. The skill applies only when the orchestrator provides the proposal, specs, and design references after the propose and design phases, capturing full context before planning begins.
sebasmzgCreate technical design documents from proposals and specs.
rodacatoCreate an ordered tasks.md checklist from an accepted SDD-lite plan.
beekeeper-labGenerate structured handoff packets documenting artifacts, decisions, assumptions, and next steps.
Asharf30Generate dependency-ordered task lists from project design artifacts and user stories.
