Mini Spec
Create a compact SPEC.md that prevents premature agreement by defining intent, non-goals, likely failure modes, and verification evidence.
Install
$ agentstack add skill-tmusser-ai-engineering-skills-mini-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-tmusser-ai-engineering-skills-mini-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
Mini Spec
Purpose
Create the smallest useful SPEC.md that clarifies intent, names the likely failure mode, and gives the agent a verifiable target before planning or implementation.
When to use
Use when a project or feature is clear enough to define before implementation.
Inputs
- Clarified request
CONTEXT.mdif available- Constraints
- Known commands
- Acceptance criteria or desired behavior
Workflow
- State the objective.
- Identify the user or use case.
- Define observable acceptance criteria.
- Record non-goals.
- List likely failure modes and name the primary failure mode for this slice.
- Record constraints.
- List run, test, build, and verification commands.
- Sketch project structure.
- Define the smallest verification demo.
- Record open questions.
- When applicable, name compatibility seams that must remain import-compatible or output-compatible.
- When applicable, record invalid-if constraints that would make the slice non-viable.
Outputs
SPEC.md- Explicit acceptance criteria
- Explicit non-goals
- Likely failure modes
- Verification demo
Compatibility seams to preserve
When applicable, list behavior that must remain import-compatible or output-compatible.
- Public imports / APIs: TBD
- CLI commands / flags: TBD
- JSON/schema/output contracts: TBD
- Existing tests whose meaning must remain valid: TBD
- Data/fixture semantics: TBD
Invalid if
- breaks a named compatibility seam
- weakens or rewrites existing tests merely to fit the implementation
- changes fixture/source data without explicit approval
- preserves behavior only through a new alternate path while breaking the old path
- changes forbidden/protected files
- adds dependencies or framework changes outside scope
Stop conditions
- The spec is under 100 lines unless risk justifies more.
- The next implementation slice is clear.
- Unresolved questions are recorded instead of hidden.
Anti-patterns
- Turning a small POC into a full product requirements document.
- Adding speculative future features.
- Writing vague acceptance criteria that cannot be verified.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: tmusser
- Source: tmusser/ai-engineering-skills
- License: MIT
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.