sdd-apply

Implements spec-driven development tasks from specs and design documents with optional strict TDD.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-apply-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-apply
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/sdd-apply
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-apply-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents often generate code without following a spec-first, test-first discipline, leading to implementations that drift from approved designs and lack test evidence. This Skill enforces a structured implementation phase where tasks from a Spec-Driven Development (SDD) workflow are executed strictly against specs and design artifacts, with progress persisted and auditable. ## Core Features & Use Cases - Task-Based Implementation: Executes assigned tasks from tasks.md (or Engram artifacts) by reading specs as acceptance criteria and design decisions as constraints, then marking tasks complete as it goes. - Strict TDD Mode: When enabled and a test runner exists, loads a dedicated TDD module enforcing RED-GREEN-TRIANGULATE-REFACTOR cycles, assertion quality rules, and a mandatory TDD Cycle Evidence table. - Multi-Backend Persistence: Supports engram, openspec, hybrid, and none artifact store modes, with merge protocols that preserve progress across batched apply runs. - Workload Governance: Enforces review workload forecasts, chained/stacked PR strategies, and size-exception gates before writing code. - Use Case: An orchestrator agent delegates "Phase 1, tasks 1.1-1.3" of an auth change; this Skill reads the proposal, spec, and design, implements the JWT middleware following existing code patterns, marks tasks [x], persists apply-progress, and returns a structured summary ready for the verify phase. ## Quick Start Delegate the pending tasks for a specific change to the sdd-apply sub-agent so it implements them according to 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 with an AI agent?▼

Delegate the specific tasks to the sdd-apply sub-agent with the change name and task range. It reads the specs as acceptance criteria, follows the design decisions, writes the code, and marks each task `[x]` in the persisted tasks artifact as it completes them.

How does strict TDD mode work in the apply phase?▼

When strict_tdd is true and a test runner exists, the Skill loads the strict-tdd.md module and enforces RED-GREEN-TRIANGULATE-REFACTOR cycles per task. It requires a TDD Cycle Evidence table, bans trivial assertions, and the verify phase rejects work missing this evidence.

Can sdd-apply work with both Engram and OpenSpec artifact stores?▼

Yes, it supports engram, openspec, hybrid, and none modes. Hybrid mode persists progress to Engram via mem_update while also updating tasks.md checkboxes on the filesystem, following both conventions simultaneously.

What happens if apply progress already exists from a previous batch?▼

The Skill reads the existing apply-progress artifact first, skips already-completed tasks, and merges prior completions with new ones when saving. Overwriting without reading prior progress is explicitly forbidden to prevent losing completed work.

When does sdd-apply stop instead of writing code?▼

It stops when applyState is blocked, when the workspace context marks edit roots as read-only, or when a workload forecast requires a chained-PR or size-exception decision that was not provided. It returns a blocked status with the reason.