sdd-apply

Implement SDD tasks from tasks.md into code matching spec and design.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/dallay/opencode-docker --skill sdd-apply-dallay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-apply
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/sdd/sdd-apply
Command: npx skills add https://github.com/dallay/opencode-docker --skill sdd-apply-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts assigned SDD change tasks into concrete, standards-compliant code while ensuring work is traceable and verifiable against specs and design documents.

Core Features & Use Cases

  • Implements individual tasks from tasks.md according to the project's spec and design, matching existing code patterns.
  • Supports both TDD (RED → GREEN → REFACTOR) and standard implementation workflows, detecting test runners and running only relevant tests.
  • Persists progress by updating tasks.md, follows openspec conventions, and returns a structured implementation summary for orchestrators.

Quick Start

Run the sdd-apply sub-agent on a change to implement the assigned tasks, mark completed items in tasks.md, and return the implementation summary.

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 change into working code?

To implement SDD tasks, apply the sdd-apply workflow to turn assigned tasks from tasks.md into code that satisfies the provided spec and design while matching existing code patterns. It updates tasks.md to persist progress and returns a structured implementation summary.

Can I use TDD to implement spec-driven design tasks?

Yes, TDD implementation is fully supported for spec-driven design tasks. The workflow detects TDD mode automatically, following the RED, GREEN, and REFACTOR cycle to ensure code is verifiable against the provided spec and design documents.

How does test detection work when implementing design tasks?

Test detection works by identifying the active test runner and running only the relevant tests required for the assigned implementation tasks. This ensures verifiable progress without executing the entire test suite unnecessarily.

Do I need to manually update tasks.md as I implement code?

No, you do not need to manually update tasks.md. The implementation workflow automatically detects completed items and persists task completion directly in tasks.md according to openspec conventions.

What is the difference between TDD mode and standard implementation for SDD changes?

TDD mode enforces a RED, GREEN, REFACTOR cycle with relevant test execution, while standard implementation mode converts assigned tasks into working code directly. Both modes ensure code matches the spec and updates tasks.md.

Why is my SDD implementation not matching the project spec?

Your SDD implementation might not match the spec if the workflow lacks access to the correct design documents or if existing code patterns are not followed. Ensure the orchestrator assigns specific tasks correctly from tasks.md.