Write executable failing tests from a caller-provided recipe.
npx skills add https://github.com/friedbotstudio/baseline --skill scenario-friedbotstudio
Please help me install this Agent Skill. Skill: scenario Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/scenario Command: npx skills add https://github.com/friedbotstudio/baseline --skill scenario-friedbotstudio
This Skill removes the guesswork from test-first work by turning a caller-provided recipe into exact failing tests, so you can drive implementation with clear, targeted coverage.
Use the scenario skill to write the exact failing tests for the provided recipe, matching the project’s test style and fixtures.
High-intent search queries and answers about installing and using this skill.
To write failing tests from a TDD recipe, provide exact recipe entries, target paths, anchor tests, and out-of-scope rules. This generates style-matched, fixture-driven tests that remain collectable and red for implementation without inventing extra scenarios.
Recipe-driven test writing matches existing pytest fixtures by following your project's current tests for imports, assertion idioms, naming, and fixture wiring. It requires anchor tests to ensure generated regression checks align with your style.
To generate failing tests for specific scenario coverage, you need to supply a caller-provided recipe with exact entries, target paths, anchor tests, and out-of-scope rules. This ensures the output tests are collectable and fail for intended reasons.
No, this approach does not invent extra test cases. It writes only the scenarios specified in the caller-provided recipe, ensuring strict scenario coverage without expanding scope or generating unexpected regression checks.
Generated tests need to fail for intended reasons to validate test-first workflows. Red-first validation confirms the new tests are collectable and fail correctly before handing them back, driving implementation with clear and targeted coverage.
Yes, you can use this for test-first workflows needing fixture-driven regression checks. It applies directly to TDD plans requiring specific scenario coverage and style-matched test files derived from a fixed recipe.
SkogAIGenerate detailed implementation plans with file paths, code samples, and tests.
AutisticAFReproduce bugs with failing tests and apply minimal fixes via red-green-refactor.
mehdicAnalyze test suites to extract fixtures, naming conventions, and patterns.
nashgaoAudit, classify, and rewrite confirmation-style tests into specification-first TDD tests.
