sdd-spec-impl

Implement development tasks via Red-Green-Refactor TDD cycles with spec adherence.

Updated Dec 2, 2025
One-click install
npx skills add https://github.com/qlawmarq/dotfiles-common --skill sdd-spec-impl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec-impl
Source: https://github.com/qlawmarq/dotfiles-common/tree/main/skills/sdd-init/references/skills/spec-impl
Command: npx skills add https://github.com/qlawmarq/dotfiles-common --skill sdd-spec-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the implementation of development tasks by strictly adhering to the Test-Driven Development (TDD) methodology, ensuring code quality and adherence to specifications.

Core Features & Use Cases

  • TDD Cycle Enforcement: Guides the Red-Green-Refactor cycle for each task.
  • Specification Adherence: Ensures implementation aligns with spec.json, requirements.md, and design.md.
  • Task Management: Updates tasks.md to mark completed tasks.
  • Use Case: Implement a new user authentication feature by writing tests for login, then writing minimal code to pass, and refactoring, ensuring all requirements are met before moving to the next task.

Quick Start

Use the sdd-spec-impl skill to implement feature 'user-auth' tasks 1.1 and 1.2.

Frequently Asked Questions about sdd-spec-impl

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

FAQPage Schema
How do I implement code using Test-Driven Development with existing specs?

Test-Driven Development implementation with existing specs is executed through a strict Red-Green-Refactor cycle, ensuring minimal code is written to pass tests while adhering to specification documents like requirements.md and design.md.

What is the best way to enforce TDD compliance during feature implementation?

TDD compliance during feature implementation is enforced by guiding the Red-Green-Refactor cycle for each task, verifying that all code aligns with approved specifications before updating task tracking files to mark completion.

Do I need spec.json and design.md files to automate development tasks?

Yes, spec.json, requirements.md, and design.md files are required inputs. The implementation process validates code against these approved specifications to ensure robust, specification-compliant task completion.

How does specification-driven development track completed implementation tasks?

Specification-driven development tracks completed implementation tasks by automatically updating a tasks.md file, marking tasks as done only after they successfully pass the TDD cycle and meet all defined requirements.

Can I implement specific feature tasks selectively using a TDD workflow?

Yes, you can implement specific feature tasks selectively by targeting individual task identifiers within the defined docs/tasks/ directory, applying the TDD workflow strictly to the chosen subsets.

When should I not use a strict Red-Green-Refactor cycle for development?

A strict Red-Green-Refactor cycle might not suit exploratory coding or prototyping phases where formal specifications are absent, as this implementation requires predefined approved tasks and specification files.