strelov1/spec-driven-tdd

using-spec-driven-tdd

Entry point for the spec-driven-tdd workflow - invoke at the START of an OpenSpec change to load the delivery discipline and hand off to the spec-driven-tdd orchestrator before writing code

First seen Jun 10, 2026

Installation

$ npx skills add strelov1/spec-driven-tdd --skill using-spec-driven-tdd

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from strelov1/spec-driven-tdd · top by installs.

npx skills add strelov1/spec-driven-tdd

Browse all from strelov1/spec-driven-tdd

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 10
License LICENSE
Default branch master
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,261 B
  • docs SUMMARY.md 218 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 40 installs

SKILL.md

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.