By craigtkhill
Spec-Test-Driven Development workflow plugin with skills for specification writing, test-driven development, and commit management
Use when writing acceptance tests or adding scenarios to spec.yaml. Defines Given/When/Then format and acceptance test patterns.
Use when creating or modifying skills. Defines skill file structure, naming conventions, and integration patterns.
Use when creating or updating agent evaluation suites. Defines eval structure, rubrics, and validation patterns.
Use when adding project dependencies. Defines dependency management rules and language-specific patterns.
Use when running pre-commit hooks manually (e.g. before committing or after implementing). This project uses prek, not pre-commit. Defines the correct commands for running hooks.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
_____ __________ ____ ___ __
/ ___//_ __/ __ / __ \ / | ____ ____ ____ / /______
\__ \ / / / / / / / / / / /| |/ __ `/ _ \/ __ \/ __/ ___/
___/ / / / / /_/ / /_/ / / ___ / /_/ / __/ / / / /_(__ )
/____/ /_/ /_____/_____/ /_/ |_\__, /\___/_/ /_/\__/____/
/____/
Spec-Test-Driven Development Agents
Agents and configs following a Spec-Test-Driven Development process
This repository is designed for Agentic Terminal User Interfaces (ATUIs) like:
STDD Agents provides a structured workflow for developing applications using ATUIs, emphasizing specification-first development with comprehensive testing to ensure stability while moving with higher velocity.
Note. The aspiration is to make this toolkit ATUI agnostic. However, it is currently heavily configured for Claude Code.
Choose your ATUI and follow the installation guide:
/plugin marketplace add https://github.com/craigtkhill/stdd-agents
/plugin install stdd-agents@stdd-agents
npx claudepluginhub craigtkhill/stdd-agents --plugin stdd-agentsSPEC-First development workflow with TDD, Ralph Loop, and autonomous agent coordination for Claude Code
Unified toolkit for Context-Driven Development with spec-first planning, TDD workflow, and Beads integration
Acceptance Test Driven Development for Claude Code. Enforces the ATDD methodology: write Given/When/Then specs first, generate a project-specific test pipeline, maintain two test streams (acceptance + unit). Inspired by Robert C. Martin's acceptance test approach from empire-2025.
Spec-driven development pipeline for Claude Code: interview-to-spec, spec-approach, tdd, verify, diagnose, and a feature orchestrator.
Spec-Driven Development for Claude Code: 18 atomic, stack-agnostic skills + 9 subagents that carry a feature from idea → spec → design → data-model → API → tasks → tests → implement → review → ship, plus a TDD implementation engine and a living roadmap above the per-feature flow. Start with `survey` (maps an existing codebase or bootstraps an empty one), walk the gated backbone — each stage reads the previous artifact and hard-refuses if missing — and keep `docs/roadmap.md` (Now/Next/Later, outcome-altitude, never dates) in sync as `specify` promotes a feature to Now and `ship` moves it to Shipped. The Q&A skills are depth-tunable (easy/medium/hard — decide-for-me vs. interrogate-me-with-trade-offs); the ideation analyses run as named subagents (researcher/strategist/analyst/devil's-advocate) gated by that dial; diagrams are presented in prose and written to file (never raw Mermaid dumped to the terminal); and every acceptance criterion is covered end-to-end. design is surface-aware: it declares the feature's target surfaces at the architecture stage (backend-service / web-frontend / mobile-app / desktop-app / cli / worker / library-sdk, each a C4 container) and downstream stages gate their output by that choice — the `ui` task layer, UI-driven sequence flows, and the component / visual-regression / e2e-through-UI frontend test tiers; `ui` work reuses the repo's existing design system (components / tokens / styling) from the architecture map, never reinvents. Every stage ends with a copy-ready handoff block — what changed, the files to review, then `/clear` + the next `/sdd:…` command.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.