Define software behavior specifications using given/when/then scenarios.
npx skills add https://github.com/dmayerdesign/spex --skill spex-specify
Please help me install this Agent Skill. Skill: spex-specify Source: https://github.com/dmayerdesign/spex/tree/main/.claude/skills/spex-specify Command: npx skills add https://github.com/dmayerdesign/spex --skill spex-specify
The specification skill helps teams articulate expected software behavior before coding, focusing on user experiences and describing outcomes in a clear, testable way.
Describe a feature by listing concrete given/when/then scenarios for immediate collaboration.
High-intent search queries and answers about installing and using this skill.
Testable acceptance criteria are written by defining concrete given/when/then scenarios that capture user interactions and outcomes. This specification workflow identifies actors, core nouns, and success criteria to ensure every feature description remains technology-free and testable.
The given/when/then format structures software behavior specification by outlining scenarios. "Given" sets the precondition, "when" describes the user interaction, and "then" defines the testable outcome, maintaining a technology-free narrative that guides design and implementation.
Specification scenarios are structured by following a process-guiding workflow that starts with happy-path interactions and progresses to error paths and edge cases. This ensures comprehensive coverage of actors, core nouns, and acceptance criteria across all features.
Yes, the specification workflow identifies core nouns and actors to ensure a consistent vocabulary across features. It enforces technology-free descriptions and clear acceptance criteria, keeping the user experience narrative uniform and testable throughout the project.
Yes, the specification approach explicitly maintains a technology-free narrative to describe expected software behavior. By focusing on user experiences and given/when/then outcomes, it guides design and tests without coupling scenarios to specific implementation technologies.
You need to define software behavior specifications before coding when teams must articulate expected user experiences and testable outcomes clearly. Using the spec workflow ensures edge cases and acceptance criteria are identified upfront, preventing ambiguous requirements during implementation.
philo-grovesAnalyze web application actors, routes, sessions, and security aspects.
AsiaOstrichGuide teams through ATDD workflows with Given-When-Then acceptance criteria.
wahidyankfEnforce structured Given-When-Then syntax for testable acceptance criteria.
zephyrwang6Create and edit JSON Canvas .canvas files with nodes, edges, and groups.
