Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Behavior Spec Writer

    1

    Turn vague specs into a verifiable BDD test matrix with GIVEN/WHEN/THEN scenarios for happy paths and edge cases.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Behavior Spec Writer

    Behavior Spec Writer

    Example session with this skill installed

    Make specs/export-users/spec.md testable. Expand the acceptance criteria and write the test matrix.

    • Read your context and instructions
    • Compiled the behavior spec writer

    I read spec.md (3 scenarios) and package.json (test framework: vitest, command npm test). I expanded the acceptance criteria to 8 scenarios covering the happy path, boundaries, errors and repetition, and wrote testing.md.

    Refined acceptance criteria (spec.md)

    • GIVEN 3 active and 1 deactivated user WHEN an admin exports THEN the CSV has a header plus 3 data rows.
    • GIVEN no users WHEN an admin exports THEN the CSV contains only the header row.
    • GIVEN exactly 50,000 active users WHEN an admin exports THEN the export succeeds.
    • GIVEN 50,001 active users WHEN an admin exports THEN the export fails with "limit exceeded" and no file is produced.
    • GIVEN an email containing a comma or a double quote WHEN exporting THEN the field is quoted and quotes are doubled.
    • GIVEN a non-admin user WHEN they request an export THEN the system responds 403 and exports nothing.
    • GIVEN the database times out mid-export WHEN an admin exports THEN the user sees a retryable error and no partial file is delivered.
    • GIVEN the same export requested twice WHEN both complete THEN both files have identical content.

    testing.md

    IDTypeGIVENWHENTHENCoverage
    TC1happy3 active + 1 deactivatedadmin exportsheader + 3 rowsintegration
    TC2edgeno usersadmin exportsheader onlyunit
    TC3edgeexactly 50,000 activeadmin exportssucceedsintegration
    TC4error50,001 activeadmin exports"limit exceeded", no fileintegration
    TC5edgeemail with comma and quoteserializequoted, quotes doubledunit
    TC6errornon-adminrequests export403, nothing exportedintegration
    TC7errorDB timeoutadmin exportsretryable error, no partial fileintegration
    TC8idempotencysame export twiceboth completeidentical contentunit

    How to run: npm test (vitest, read from package.json).

    Next steps

    1. Review TC3 and TC4: they need a generator for 50,000 and 50,001 rows.
    2. When the cases look right, turn them into tests with spec-to-tests.

    PASS

    Refined acceptance criteria (spec.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Vague acceptance criteria lead to brittle code and missed edge cases. This skill transforms high-level requirements into a verifiable GIVEN/WHEN/THEN test suite. It forces a rigorous assessment of boundary conditions and error states before a single line of test code is written.

    What it does

    • Requirement expansion converts basic acceptance criteria into at least 6 detailed GIVEN/WHEN/THEN scenarios.
    • Edge case discovery identifies boundary conditions like empty states, timeouts, and permission failures.
    • Matrix generation creates a structured testing.md file mapping scenarios to specific test types.
    • Tech stack detection reads your project manifest to ensure test instructions match your actual frameworks.
    • Gap analysis flags contradictory requirements or insufficient detail as blocking issues.

    How it works

    1. The skill audits spec.md and related design docs to extract current requirements.
    2. It inspects your project configuration to identify existing test runners and libraries.
    3. It updates spec.md with expanded BDD scenarios and generates a comprehensive testing.md matrix.

    Frameworks & tools

    This skill adapts to your environment by reading package.json, pyproject.toml, or similar manifests. It supports Gherkin-style BDD syntax and works with any testing stack including Jest, Pytest, Playwright, or Vitest.

    Why this beats prompting it yourself

    Generic prompts often miss non-happy path scenarios like idempotency or dependency failures. This skill enforces a strict minimum of six scenarios across four specific categories, ensuring coverage that manual prompting usually overlooks.

    Use cases

    • Generating a test plan for a new feature from a rough proposal.
    • Hardening a spec before a handoff from design to engineering.
    • Auditing existing requirements for missing error handling and boundary checks.

    Known limitations

    Requires a spec.md file to function. It will not write executable test code unless specifically requested, focusing instead on the behavioral logic and test plan.

    Requires an existing spec.md file. Does not generate executable test code by default. Execution stops if fewer than 3 scenarios are viable.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 19 days ago

    Permissions

    Read Files
    Write Files
    Listed19 days ago

    What's inside

    Frequently Asked Questions

    This skill bridges the gap between vague product ideas and technical implementation by transforming high-level requirements into a structured BDD matrix (GIVEN/WHEN/THEN), ensuring edge cases and error states are documented before coding begins.

    The skill automatically detects your tech stack by reading files like package.json or pyproject.toml, ensuring the generated test scenarios and testing.md matrix align with your specific tools like Jest, Pytest, or Playwright.

    No, this skill focuses on the logic layer; it generates a comprehensive behavioral test plan and Gherkin-style scenarios in Markdown, which then serve as the blueprint for your agent or engineers to write the actual test code.

    The skill requires an initial spec.md file or design document to analyze; if your requirements are too thin, its built-in Gap Analysis will flag specific missing details as 'blocking issues' rather than guessing.

    While standard prompts often stick to the 'happy path,' this skill enforces a strict discovery protocol that mandates at least six scenarios covering boundary conditions, timeouts, and permission failures.

    New in Testing & Debugging