mcpField
U
using-spec-driven-tdd

using-spec-driven-tdd

github.com/strelov1Agent workflows1356 installsUpdated 12w ago
Repository

About using-spec-driven-tdd

A workflow skill for implementing OpenSpec changes with planning, TDD, review, and archiving. It combines OpenSpec change tracking with Superpowers practices and directs coding agents to invoke the workflow before implementation.

Key features

  1. 01Plan and track changes in OpenSpec
  2. 02Use TDD during implementation
  3. 03Simplify and review code
  4. 04Apply systematic debugging practices
  5. 05Finish and archive changes

Use cases

  1. 01Start implementation of an OpenSpec change
  2. 02Apply a requested change using a tracked workflow

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/strelov1/spec-driven-tdd --skill using-spec-driven-tdd

After installing, type/using-spec-driven-tddin Claude Code to confirm it loaded.

Details

From the project README

Using spec-driven-tdd

You have the spec-driven-tdd workflow: plan and track in OpenSpec, implement with Superpowers discipline (TDD, simplify, review), finish and archive.

The rule

When you are about to implement an OpenSpec change — or the user asks to build, apply, or work through a change — invoke the spec-driven-tdd skill BEFORE writing code, and follow its steps rather than improvising.

If a 1% chance it applies, invoke it. Knowing the lifecycle is not the same as following it.

What it composes

  • Plan / track: OpenSpec (/opsx:propose, /opsx:apply, /opsx:archive, /opsx:sync).
  • Execute: Superpowers (test-driven-development, requesting-code-review, receiving-code-review, systematic-debugging, using-git-worktrees, verification-before-completion, finishing-a-development-branch) plus this pack's simplify skill.

Dependencies and graceful degradation: see docs/dependencies.md.

Invoke spec-driven-tdd now if you are starting implementation.

Comments

Markdown supported