sdd-apply

Implements SDD change tasks by writing code from specs and design artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns approved spec-driven development (SDD) plans into actual working code, executing assigned tasks from tasks.md while strictly following the specs and design documents instead of improvising. ## Core Features & Use Cases - Task Implementation: Reads proposal, spec, design, and tasks artifacts, then writes code for only the assigned tasks and marks them complete in the persisted tasks artifact. - Strict TDD Mode: When strict TDD is enabled and a test runner exists, it loads a dedicated module enforcing RED-GREEN-REFACTOR cycles with a mandatory TDD Cycle Evidence table. - Progress Persistence: Saves cumulative apply-progress artifacts across batches (engram, openspec, or hybrid modes) so no completed work is lost between runs. - Workload Governance: Enforces review workload decisions (chained PRs, stacked PRs, or size exceptions) before writing code, and stops when the apply state is blocked or unsafe. - Use Case: An orchestrator assigns Phase 1 tasks 1.1-1.3 of an authentication change; the skill reads the JWT spec scenarios, implements the middleware following the design, runs focused tests, and returns a structured summary ready for the verify phase. ## Quick Start Delegate the pending tasks for your change to the sdd-apply sub-agent so it implements them from the specs and design artifacts.

Frequently Asked Questions about sdd-apply

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

FAQPage Schema
How do I implement SDD tasks from a tasks.md file?▼

Delegate the assigned tasks to the sdd-apply sub-agent with the change name and task range. It reads the spec scenarios as acceptance criteria, follows the design decisions, writes the code, and marks each task complete in the persisted tasks artifact.

What is strict TDD mode in spec-driven development?▼

Strict TDD mode activates when strict_tdd is true and a test runner exists. It loads a dedicated module enforcing RED-GREEN-REFACTOR cycles with mandatory triangulation, and requires a TDD Cycle Evidence table that the verify phase checks.

Can sdd-apply resume work from a previous batch?▼

Yes. It searches for an existing apply-progress artifact, parses which tasks are already complete, skips them, and merges prior completions with new ones when saving progress so no completed work is lost.

Why does sdd-apply stop before writing code?▼

It stops when applyState is blocked, when the workload forecast requires an unresolved delivery decision, or when edits fall outside allowed roots. In these cases it returns a blocked status describing the missing decision or unsafe path.

What artifact stores does sdd-apply support?▼

It supports engram (memory-based topics), openspec (filesystem tasks.md), hybrid (both), and none (return progress only). The mode determines how tasks are read, marked complete, and how apply-progress is persisted.