sdd-implement

Executes approved spec-driven development cycles using test-driven RED-GREEN-REFACTOR triads.

1|Updated Jul 26, 2026
One-click install
npx skills add https://github.com/AngeloResplandes/harness-sdd --skill sdd-implement-angeloresplandes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-implement
Source: https://github.com/AngeloResplandes/harness-sdd/tree/main/sdd-implement
Command: npx skills add https://github.com/AngeloResplandes/harness-sdd --skill sdd-implement-angeloresplandes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It turns an approved implementation plan into working code without losing discipline: tasks are executed in order, every behavior change is backed by a failing test first, and progress is recorded in tasks.md so an interrupted session can resume accurately. ## Core Features & Use Cases - Gate enforcement: Refuses to run unless plan.md has status approved, verifies the declared git branch, and never writes into spec/ or checks off the final promote task. - TDD triad execution: Works tasks.md as RED/GREEN/REFACTOR trios, recording the observed failure message on each RED task as durable proof, with stop rules after 2 failed debugging hypotheses or 3 failed GREEN attempts. - Scoped correction rounds: After a failed verification or validation, works only the listed gaps or the matching Correções section, keeping fixes reviewable. - Use Case: A user says "pode implementar" after approving a plan; the skill resolves the newest cycle, runs each triad with a failing test first, checks off tasks as it goes, stops at stage boundaries for review, and hands off to verification. ## Quick Start Say "implementa o ciclo" after approving the plan, and the skill will execute the tasks with test-driven discipline and report progress.

Frequently Asked Questions about sdd-implement

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

FAQPage Schema
How do I implement an approved plan with test-driven development?

Approve the plan first so plan.md shows status approved, then ask to implement the cycle. The skill works tasks.md as RED-GREEN-REFACTOR triads, writing a failing test before any production code and checking tasks off as it goes.

What happens if I try to implement before the plan is approved?

The skill refuses to run against a draft plan. It treats the frontmatter status field as the record of approval, not the conversation, and asks you to approve the plan first through the refine step.

Can it resume an interrupted implementation session?

Yes. Progress is recorded by checking off tasks in tasks.md as they complete, so a new session reads the file to see exactly where work stopped and continues from the first unchecked task.

How does it handle fixes after a failed validation?

It reads validation.md, takes the attempt number, and works only the matching Correções section in tasks.md plus any tasks validation unchecked. The final promote task is explicitly excluded from its scope.

When does the skill stop and ask for human input?

It stops after two failed debugging hypotheses or three failed GREEN attempts, on broken state like missing tasks.md or a branch mismatch, and at each stage boundary in large cycles, reporting what happened rather than guessing further.