sdd-apply

Convert task descriptions and specs into executable code for orchestrated projects.

1.3k|159|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-apply
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-apply
Source: https://github.com/Gentleman-Programming/agent-teams-lite/tree/main/skills/sdd-apply
Command: npx skills add https://github.com/Gentleman-Programming/agent-teams-lite --skill sdd-apply

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill enables an orchestrator-driven sub-agent to implement tasks from a change by translating specifications and design into concrete code, ensuring consistent follow-through and traceability.

Core Features & Use Cases

  • Implement tasks exactly as specified by a change, following the provided specs and design.
  • Manage the RED-GREEN-REFACTOR cycle when in TDD mode and update progress in tasks.md.
  • Respect the project's persistence contracts (engram/openspec/none) and return a structured progress summary.
  • Works across standard and TDD workflows within an orchestrated agent-team pattern.

Quick Start

Instruct the agent to read the change context, determine the workflow mode, perform the RED-GREEN-REFACTOR cycle when in TDD mode, update tasks.md, and return a structured implementation progress summary.

Frequently Asked Questions about sdd-apply

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

FAQPage Schema
How do I convert specifications into working code automatically?

Spec-driven coding converts specifications into working code by using an orchestrator-driven sub-agent to translate task descriptions and design documents directly into concrete, executable code artifacts.

How does TDD workflow orchestration handle the RED-GREEN-REFACTOR cycle?

TDD workflow orchestration manages the RED-GREEN-REFACTOR cycle by automatically executing test failures, implementing code to pass tests, and refactoring, while persisting task progress updates in tasks.md.

Can I use sub-agent orchestration for projects without a persistence contract?

Yes, sub-agent orchestration supports projects without a persistence contract by adapting to the 'none' persistence mode, alongside supporting engram and openspec contracts for structured artifact persistence.

What is the best way to manage code generation tasks across multiple phases?

Managing code generation tasks across multiple phases is best handled by an orchestrated agent-team pattern that delegates work to specialized sub-agents, ensuring consistent spec-following and structured progress reporting.

Do I need an orchestrator to apply task descriptions and specs to my codebase?

Yes, you need an orchestrator to apply task descriptions and specs because the system operates within an orchestrated software project framework where a coordinator delegates implementation work to specialized sub-agents.

Why does spec-driven code generation require a structured progress summary?

Spec-driven code generation requires a structured progress summary to ensure traceability and consistent follow-through across orchestrated sub-agents, satisfying artifact persistence contracts and workflow reporting requirements.