sdd-tasks

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

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/albersg/dotfiles --skill sdd-tasks-albersg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-tasks
Source: https://github.com/albersg/dotfiles/tree/main/dotfiles-opencode/.opencode/skills/sdd-tasks
Command: npx skills add https://github.com/albersg/dotfiles --skill sdd-tasks-albersg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved specification-driven development (SDD) design into concrete, ordered implementation work is error-prone: tasks end up vague, unordered, or missing test coverage. This Skill converts a change's proposal, specs, and design into a structured tasks.md with dependency-ordered phases and verifiable checklist items. ## Core Features & Use Cases - Phased Task Breakdown: Produces hierarchical tasks (1.1, 1.2, 2.1...) organized into Foundation, Core Implementation, Integration, Testing, and Cleanup phases, each task specific, actionable, and verifiable. - Review Workload Forecast: Estimates changed-line volume against a 400-line review budget and recommends chained or stacked PR splits with focused test commands, runtime harnesses, and rollback boundaries. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, reading dependencies and persisting the tasks artifact accordingly. - Use Case: After an orchestrator completes the design phase for a new authentication feature, this sub-agent generates tasks.md with RED-test-first tasks derived from the threat matrix, plus a PR-chaining recommendation when the change exceeds the review budget. ## Quick Start Ask the orchestrator to run the sdd-tasks phase for your change so it produces a tasks.md breakdown with phases, test tasks, and a review workload forecast.

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 to the sdd-tasks sub-agent with the change name, artifact store mode, and delivery strategy. It reads the proposal, specs, and design, then produces a tasks.md with dependency-ordered phases and concrete, verifiable checklist items.

What makes a good implementation task in a tasks.md file?▼

Each task must be specific (name the file and change), actionable, verifiable with a test or check, and small enough to complete in one session. Vague entries like "implement feature" or "add tests" are explicitly rejected.

How does the 400-line review budget affect task planning?▼

The skill estimates changed lines and flags Low, Medium, or High budget risk. When risk is High, it recommends chained PRs, splits work into autonomous units with test commands and rollback boundaries, and asks the user to choose a chain strategy.

Can sdd-tasks run without writing files to the repository?▼

Yes. In engram mode it persists the tasks artifact to Engram storage only, and in none mode it returns the result inline without creating or modifying any project files. Only openspec and hybrid modes write tasks.md to disk.

Why must threat-matrix cases become RED-test tasks first?▼

Every applicable threat-matrix case from the design must map to an explicit failing-test task before its production task, preserving the expected safe or failure behavior. Rows marked N/A are the only ones omitted.