sdd-implement

Automate a TDD workflow from tasks.md and spec files.

1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/eburairu/Squat-Tracker --skill sdd-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-implement
Source: https://github.com/eburairu/Squat-Tracker/tree/main/.agent/skills/sdd-implement
Command: npx skills add https://github.com/eburairu/Squat-Tracker --skill sdd-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates following a predefined task list (tasks.md) and enforces a strict test-driven development (TDD) cycle to drive implementation progress.

Core Features & Use Cases

  • Spec-driven iteration: Reads target spec from .sdd/target-spec.txt and steering info (product.md, tech.md, structure.md) to guide implementation.
  • Automated task execution: Processes tasks.md in order, performing red/green/refactor/update steps until tasks are complete.
  • TDD discipline: Ensures tests are written first (RED), implemented to pass (GREEN), refactored, and updated in tasks.md.

Quick Start

  • Review the target spec and steering docs, then start the cycle with a command like "実装開始" or "start coding" to trigger the flow. Then follow the prompts to create tests, implement code, refactor, and update tasks.md.

Frequently Asked Questions about sdd-implement

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

FAQPage Schema
How do I automate a TDD workflow using a tasks.md specification?

To automate a TDD workflow, this Skill reads your tasks.md list and spec files, then executes a deterministic RED-GREEN-Refactor-Update loop across each task. It processes tasks sequentially, writing tests first and implementing code to pass them.

What files do I need to set up before starting spec-driven TDD implementation?

You need to create a .sdd/target-spec.txt file for target specs, along with product.md, tech.md, and structure.md for steering data. Tasks.md and related spec documents must also exist to guide the automated TDD cycle.

How does the RED-GREEN-Refactor cycle work with a tasks.md list?

The RED-GREEN-Refactor cycle enforces TDD discipline by first writing a failing test (RED), implementing code to make it pass (GREEN), refactoring the code, and finally updating tasks.md. This strict sequence is applied to every task in the list.

What is the best way to enforce strict test-driven development when implementing features?

The best way to enforce strict test-driven development is using an automated TDD workflow driven by a tasks.md specification. It prevents skipping steps by deterministically processing the RED, GREEN, Refactor, and Update phases for each feature.

Can I trigger automated TDD cycles from a single command?

Yes, you can trigger automated TDD cycles by entering a command like "start coding" or "実装開始". The Skill then reads your steering data and tasks.md to sequentially execute the test-driven implementation loop.