sdd-tdd-workflow

Guide AI agents through SDD and TDD workflows with RFC/ADR documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/inchan/zettel-memory --skill sdd-tdd-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-tdd-workflow
Source: https://github.com/inchan/zettel-memory/tree/main/.claude/skills/sdd-tdd-workflow
Command: npx skills add https://github.com/inchan/zettel-memory --skill sdd-tdd-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clear, actionable guidance for AI agents to apply a structured Specification-Driven Development (SDD) and Test-Driven Development (TDD) workflow to plan, implement, and verify complex features, ensuring specification-led outcomes.

Core Features & Use Cases

  • Specification-first planning: RFCs and ADRs define scope and design before coding.
  • Test-driven execution: Derive tests from specifications and drive implementation via Red-Green-Refactor.
  • Iterative verification: Validate against specs, update documentation, and refine with stakeholder feedback.

Quick Start

Draft an RFC or ADR, derive tests, implement via Red-Green-Refactor, and verify against the spec.

Frequently Asked Questions about sdd-tdd-workflow

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

FAQPage Schema
How do I implement specification-driven development and test-driven development together with an AI agent?

Specification-driven development and test-driven development combine by using RFCs and ADRs to define scope before coding, then deriving tests from those specifications to drive implementation via the Red-Green-Refactor cycle. This ensures specification-led outcomes with iterative verification.

When should I use an SDD and TDD workflow for complex features?

An SDD and TDD workflow is needed for complex features, architectural decisions, and large-scale refactors where clear specifications, RFC or ADR documents, test strategies, and iterative verification against stakeholder feedback are required before implementation.

How do I start a test-driven development cycle from an RFC or ADR specification?

To start test-driven development from specifications, draft an RFC or ADR to define the design scope, derive tests directly from that specification, implement code through the Red-Green-Refactor cycle, and store artifacts under docs/specs and references for review.

Can AI agents review and verify code against specifications automatically?

AI agents can review and verify code against specifications by validating the implementation iteratively, updating documentation, refining based on stakeholder feedback, and ensuring the tests and code accurately reflect the original specification documents.

What are the limitations of using a specification-driven workflow for AI-assisted coding?

A specification-driven workflow requires upfront investment in RFC and ADR documents and structured test strategies, which may introduce overhead for simple tasks that do not need complex architectural decisions or large-scale refactoring.

Does specification-driven development work better than standard test-driven development for large-scale refactoring?

Specification-driven development improves upon standard test-driven development for large-scale refactoring by enforcing that RFCs and ADRs define the architectural scope first, ensuring tests are derived from clear specifications rather than existing implementation behavior.