sdd-tasks

Generates phased implementation task breakdowns from SDD proposals, specs, and designs.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AD-Paladins/beaconator-web --skill sdd-tasks-ad-paladins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/AD-Paladins/beaconator-web/tree/main/.config/opencode/skills/sdd-tasks
Command: npx skills add https://github.com/AD-Paladins/beaconator-web --skill sdd-tasks-ad-paladins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved spec-driven development (SDD) design into concrete, ordered implementation work is error-prone: tasks end up vague, unordered, or too large to review. This Skill converts a change's proposal, specs, and design into a structured tasks.md with dependency-ordered phases and a review workload forecast. ## Core Features & Use Cases - Phased Task Breakdown: Produces hierarchical, dependency-ordered tasks (1.1, 1.2, 2.1...) across foundation, implementation, integration, testing, and cleanup phases, each referencing concrete file paths. - Review Workload Forecast: Estimates changed-line volume against a 400-line review budget and recommends chained or stacked PR splits with test commands, runtime harnesses, and rollback boundaries per work unit. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, reading upstream artifacts and persisting the tasks artifact accordingly. - Use Case: An orchestrator delegates planning for a new change; the sub-agent reads the design, emits a tasks.md with RED-test-first tasks for every threat-matrix case, and returns a summary with the recommended PR chain strategy. ## Quick Start Ask the orchestrator to run task planning for your SDD change so it delegates to the sdd-tasks sub-agent and produces a tasks.md breakdown.

Frequently Asked Questions about sdd-tasks

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

FAQPage Schema
How do I break an SDD change into implementation tasks?▼

Delegate task planning to the sdd-tasks sub-agent with the change name, artifact store mode, and delivery strategy. It reads the proposal, spec, and design, then produces a tasks.md with dependency-ordered phases and concrete file-level tasks.

What is the 400-line review budget in task planning?▼

The review workload forecast estimates whether implementation will exceed 400 changed lines. If risk is Medium or High, tasks are split into work units with focused test commands, runtime harnesses, and rollback boundaries for chained or stacked PRs.

Can the tasks artifact be stored outside the filesystem?▼

Yes. In engram mode the tasks persist to the Engram topic sdd/{change-name}/tasks without creating files; in none mode the result is returned inline only. Openspec and hybrid modes write tasks.md to openspec/changes/{change-name}/.

Why must the orchestrator not execute this skill inline?▼

The skill is marked delegate_only and user-invocable false, so the orchestrator must delegate to the dedicated sdd-tasks sub-agent. Executing inline bypasses the executor contract and the shared phase persistence rules.

How are threat-matrix cases handled in task breakdowns?▼

Every applicable threat-matrix case from the design becomes an explicit RED-test task placed before its production task, preserving the expected safe or failure behavior. Rows marked N/A are omitted.