Why does specify extension add tdd fail?
The extension is listed in Spec Kit's community catalog, which is discovery only
(install_allowed: false). The CLI shows it but does not install it.
Install directly with --from <release-zip-url>. Full steps are in
install help.
Why not just tell the agent to write tests first?
Because that is an instruction, and what you need is evidence. An agent asked to be
test-driven will produce a test file and an implementation in one pass and sincerely
describe the result as test-driven. Nothing in the output distinguishes that from a
real cycle. What makes it checkable is the ordering being recorded as it happens,
and a separate pass with no memory of the session cross-checking that record against
git history.
Which language does it support?
All of them, because it does not know any of them.
/speckit.tdd.setup detects the stack from your manifests, scripts, CI
config, and test layout, runs each command to prove it works, and writes them to a
profile the other commands read. Starting points are documented for JS and TS,
Python, JVM, .NET, Go, Rust, Ruby, PHP, Swift, Elixir, C and C++, and Dart, along
with their coverage, mutation, and property-based tooling. Detection always wins
over the table.
That is a claim worth checking rather than believing, so
the same cycle is shown above in five ecosystems. The
behavior text on the test list is identical in all five; three lines per cycle
differ, and all three are quoted from the runner rather than composed.
Will it edit my tests to make them pass?
No. That is the hardest rule in the extension: no loosened assertion, no widened
tolerance, no value check turned into a truthiness check, no skip, no narrowed
filter, no lowered threshold. When a test and the code disagree,
spec.md decides which is wrong. The audit checks the branch diff for
exactly these edits, and any of them is a FAIL condition on its own.
Does it work on legacy code with no tests?
That case is planned for explicitly. A component the feature must change but which
has no tests gets characterization behaviors first: tests that capture what the code
does today, including behavior that looks wrong, as a baseline. They are verified
with a deliberate mutant so a vacuous baseline cannot slip through, and they are
scheduled before the behaviors that change that component.
Is mutation testing required?
No, and it is scoped when it runs: only the files the feature changed, with the
scope reported alongside the score so numbers stay comparable. Where the ecosystem
has no mutation tool, the audit uses deliberate mutants on the highest-risk
behaviors instead, and states how many were sampled so the report cannot read as
exhaustive.
I squash my branches. Does that break it?
It costs you the strongest evidence. The audit's PROVEN class needs git history to
corroborate that the test changed with or before the source, and a squashed branch
loses that ordering. Those behaviors become LIKELY, which does not block a pass but
caps the verdict at PASS_WITH_GAPS. Keep the per-cycle commits until after the audit
and squash on merge instead.
How does it relate to the BDD and testing extensions?
It composes with them rather than replacing them. Gherkin scenarios from the
bdd extension become outer-loop behaviors, generated scaffolds become
list items the loop still has to drive to red, and existing traceability or
coverage-drift reports become corroboration in the audit. The gap this fills is the
loop discipline and the test-strength check, which nothing else in the catalogue
does.
How does it interact with /speckit.converge?
/speckit.converge appends unbuilt work to tasks.md as new
tasks with no behavior ids, so /speckit.implement would build them
test-after. The after_converge hook offers
/speckit.tdd.plan at that moment. The plan keeps every behavior id,
state, and cycle-log entry, and gives each new behavioral task a behavior id and a
test task before it. Then run /speckit.implement again, and the loop
builds that work test-first. If converge appended tasks and you declined the prompt,
run /speckit.tdd.plan before /speckit.implement.
Does the extension run by itself?
No. The commands are Markdown prompts. They need a Spec Kit-aware assistant to
resolve and execute them. The release zip is portable and has no runtime of its own.
How do I update the extension?
Run the install command with the newer release URL and add --force.
Your specs/ tree and your stack profile are not touched.