sdd-apply

Implement SDD tasks into code and tests with TDD or standard modes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements discrete implementation tasks defined in SDD change artifacts so engineers can reliably convert design and spec items into tested, committed code and progress records.

Core Features & Use Cases

  • Spec-first implementation: Enforces reading proposal, spec, and design artifacts before writing code so implementations match acceptance criteria.
  • TDD and standard workflows: Supports RED→GREEN→REFACTOR for TDD projects and a standard implement-then-report flow for non-TDD projects.
  • Progress persistence: Updates tasks artifacts on filesystem or engram (mem_update/mem_save) depending on the project's artifact mode, enabling downstream verification and orchestration.

Quick Start

Implement the assigned SDD tasks by reading the spec and design, writing the required code or tests according to detected workflow, and update tasks.md or the project's engram artifacts to record progress.

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 into working code from a spec and design?

To implement SDD tasks into working code, read the proposal, spec, and design artifacts to understand acceptance criteria, then write minimal code or focused failing tests based on the detected workflow mode.

How does TDD mode work when applying SDD implementation tasks?

TDD mode for SDD implementation follows the RED→GREEN→REFACTOR cycle by writing focused failing tests first, then writing passing code, ensuring software changes match the design specifications.

Can I use this to track progress in tasks.md or do I need engram?

You can track progress by updating tasks.md on the filesystem or by using engram mem_update and mem_save calls, depending on the project's artifact mode for persisting implementation records.

What's the best way to automate converting design specs into tested code?

Automating conversion of design specs into tested code requires a spec-first approach that enforces reading design artifacts before writing code, supporting both TDD and standard implement-then-report workflows.

Do I need proposal and spec artifacts before starting SDD code generation?

Yes, you need proposal, spec, design artifacts, and a tasks.md file defining discrete implementation subtasks before starting SDD code generation to ensure implementations match acceptance criteria.