Mastermind Tdd
Test-first loop — write a failing test, make it pass with the minimum, then refactor while green. Use for logic with clear inputs/outputs, for bug fixes (write the failing repro first), or when you want tests to pressure the design. Skip for throwaway spikes and pure-visual work.
Install
$ agentstack add skill-mehrad-dm-mastermind-mastermind-tdd ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mehrad-dm-mastermind-mastermind-tdd) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
MasterMind — TDD
Red → Green → Refactor (Beck). Tests first isn't dogma — it's design pressure and a safety net that lets you move fast without fear. Behavior, not implementation (~/.mastermind/engineering/fields/frontend/stack-defaults.md → Testing).
Opt-in, not a default. Writing tests / adopting TDD is a project choice — reach for this when the project already tests or the user wants tests (ask first — ~/.mastermind/engineering/core/rigor.md). To just confirm a change works without a persistent suite, use mastermind-verify instead. Verifying is never optional; a test suite is.
The loop
- Red — write ONE small failing test that states the next behavior you want (for a bug: a test that
reproduces it). Run it; watch it fail for the right reason.
- Green — write the minimum code to pass. No gold-plating, no speculative generality.
- Refactor — with the test green, improve the design (deep modules, clear names) — behavior
unchanged, tests still green. Then loop.
Rules
- One test at a time; keep the suite green between steps.
- Test behavior/contracts, not internals — brittle tests that assert implementation are worse than none.
- The test names document the spec; make them read like sentences.
- Stuck making a test pass cleanly? The design is probably wrong — that's the signal, listen to it.
Output
Passing tests + the implementation they drove, plus a one-line note on the behavior now covered.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mehrad-dm
- Source: mehrad-dm/mastermind
- License: MIT
- Homepage: https://mastermind.mehrad.me
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.