build-scenario-tests
Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code. Use when asked to add scenario tests, compile acceptance criteria or Given/When/Then Markdown into executable tests, reproduce a user-visible regression, or convert a narrow workflow specification into stable web, API, CLI, desktop, or mobile interaction coverage. Do not use for broad exploratory journeys or agent-judged smoke tests.
npx skills add tamdogood/builder-essential-skills --skill build-scenario-tests --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Build Scenario Tests Compile one small behavior contract into deterministic, repository-native test code. Understand the host project before choosing a harness, command, fixture, selector, or assertion. ## Operating contract - Treat repository instructions and existing tests as authoritative. - Keep each scenario focused on one behavior and one reason to fail. - Compile into the test stack the repository already uses. Add a dependency only when no suitable harness exists and the user accepts the tradeoff. - Make setup, inputs, actions, and expected results deterministic. - Prefer public behavior over implementation details. Assert what a user or external caller can observe. - Keep the Markdown scenario beside the test or in the repository's established specification directory. Record the mapping in both artifacts. - Never weaken an assertion merely to make a test pass. ## Workflow ### 1. Pass the repository-understanding gate Read the nearest `AGENTS.md` or equivalent instructions, product README, contribution guide, manifests, test configuration, and the smallest relevant product documentation. Use repository search to find the implementation entry point, neighboring tests, fixt
- Operating contract
- Workflow
- 1. Pass the repository-understanding gate
- 2. Normalize the scenario
- 3. Map intent to the host test stack
- 4. Compile the deterministic test
- 5. Prove the compilation
- 6. Hand off the evidence
- Demonstration examples
- Failure handling
What does the build-scenario-tests skill do?
Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code. Use when asked to add scenario tests, compile acceptance criteria or Given/When/Then Markdown into executable tests, reproduce a user-visible regression, or convert a narrow workflow specification into stable web, API, CLI, desktop, or mobile interaction coverage. Do not use for broad exploratory journeys or agent-judged smoke tests.
How do I install it?
Run `npx skills add tamdogood/builder-essential-skills --skill build-scenario-tests --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tamdogood/builder-essential-skills, a repository with 90 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.