Mastermind Spec
Turn a fuzzy request into a crisp, buildable spec before coding — problem, in/out scope, interfaces, acceptance criteria, and edge cases. Use when the ask is ambiguous, spans multiple files, or you'll hand it off to another session. Skip for a clear one-line change.
Install
$ agentstack add skill-mehrad-dm-mastermind-mastermind-spec ✓ 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-spec) 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 — Spec
A precise spec is cheaper than a wrong build. Time spent making the spec exact pays off more than time watching the implementation (~/.mastermind/engineering/core/product-sense.md, ~/.mastermind/engineering/core/agent-loop.md). This produces the what, not the code.
Write the spec
- Problem & outcome — the real user/business outcome, in one or two lines (not the literal request
if they differ). What outcome, for whom, why now?
- Scope — what's in, and explicitly what's out (deferred as follow-ups). A coherent slice.
- Interfaces & data — the files/modules touched, the key types, the API/data contracts.
- Acceptance criteria — observable behavior that means "done," from the user's view (not "compiles").
- Edge cases & failure modes — null/empty/loading/error/many/offline/unauthorized/malformed.
- Verification — the end-to-end check that proves it works.
Rules
Decide everything technical yourself; surface only genuine product trade-offs to the user (one line each). Keep it self-contained — a fresh session should be able to build from it alone.
Output
A short SPEC.md (or inline): problem, scope, interfaces, acceptance, edge cases, verification. Decisive, not a menu — the blueprint an implementer follows without second-guessing.
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.