acceptance-tests-as-specifications

Rules for treating acceptance test files and DSL stubs as the authoritative specification — read them first, work outside-in, never modify them

Skill by MoltenRuby

IndexedMIT

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/moltenruby-acceptance-tests-as-specifications

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Rules for treating acceptance test files and DSL stubs as the authoritative specification — read them first, work outside-in, never modify them

Use cases: testing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/acceptance-tests-as-specifications

What's inside

Skill name: acceptance-tests-as-specifications
Description: Rules for treating acceptance test files and DSL stubs as the authoritative specification — read them first, work outside-in, never modify them
License: MIT
Compatibility: opencode
Instructions: 17 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

## Acceptance tests as executable specifications

When you receive an acceptance test file and DSL stub file as part of your input, these are the authoritative specification
for the feature. They take priority over prose descriptions in requirements or analysis files.

- **The acceptance test file IS the specification.** Read it first. Every test case describes a required behaviour. Your job
  is to make all tests pass.
- **DSL stubs define the interface contract.** The DSL helper function signatures are the boundary between the test layer and
  the SUT. Implement the stubs to call the real domain logic — do not change the signatures.
- **Work outside-in.** Start by implementing the DSL stub functions (the outermost layer), then build the domain logic they
  need inward.
- **Verify incrementally.** After implementing each DSL stub, run the acceptance tests. Report which tests now pass and which
  still fail.
- **Never modify the acceptance test file or DSL function signatures.** If a test seems wrong, stop and ask the user — do
  not "fix" the spec.

From MoltenRuby/MrSmith, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Mar 22, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/MoltenRuby/MrSmith
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from MoltenRuby

Cite this page

acceptance-tests-as-specifications skill. Agent Mart. https://agentmart.dev/skills/moltenruby-acceptance-tests-as-specifications (last updated 2026-10-24)