sdd-apply

Translate change specifications into documented code via the SDD pipeline.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jota-batuta/batuta-dots --skill sdd-apply-jota-batuta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-apply
Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/sdd-apply
Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill sdd-apply-jota-batuta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates change specifications into production-grade code while enforcing a formal SDD process, ensuring prerequisites are verified and decisions are documented for stakeholders.

Core Features & Use Cases

  • Enforces the Execution Gate and the SDD workflow before coding.
  • Reads specs, design, and tasks to generate code with documentation and rationale.
  • Updates tasks.md and returns a structured implementation envelope suitable for auditing.

Quick Start

Provide end-to-end task implementation by validating prerequisites, generating production-ready code with module docs, and updating progress in tasks.md.

Frequently Asked Questions about sdd-apply

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

FAQPage Schema
How do I automate code generation from task specifications?

Automate code generation from task specifications by processing specs, design documents, and tasks.md through an SDD pipeline that produces production-grade code artifacts with module-level docstrings and WHY comments.

What is the Execution Gate in spec-driven development?

The Execution Gate in spec-driven development enforces prerequisite validation before coding begins, ensuring all specs, design documents, and project configurations are verified and decisions are formally documented.

How do I keep tasks.md updated when generating code across multiple tasks?

Update tasks.md during multi-task code generation by running an SDD pipeline that automatically modifies the file to reflect implementation progress alongside generating documented, testable code artifacts.

Can I generate production-grade code with documentation directly from change specifications?

Generate production-grade code with documentation from change specifications by translating them through an SDD workflow that adds module-level docstrings, WHY comments, and a structured implementation envelope to the output artifacts.

Do I need project configuration and design docs to generate task-driven code?

Task-driven code generation requires project configuration, design documents, and specifications as inputs to pass the Execution Gate validation and ensure generated artifacts align with the intended architecture.

What is the best way to ensure generated code includes rationale for stakeholder auditing?

Ensure generated code includes rationale for auditing by using a spec-driven development pipeline that outputs a structured implementation envelope containing WHY comments and module-level docstrings that document decisions for stakeholders.