Outline Given/When/Then behavioral test scenarios before coding.
npx skills add https://github.com/gustavofsantos/dot-files --skill test-design-gustavofsantos
Please help me install this Agent Skill. Skill: test-design Source: https://github.com/gustavofsantos/dot-files/tree/main/skills/test-design Command: npx skills add https://github.com/gustavofsantos/dot-files --skill test-design-gustavofsantos
Collaborative specification protocol to define the behavioral contract of a unit before any code is written. Use this skill when the user wants to think through what to test before implementing anything. Trigger on phrases like "let's figure out what to test", "before we write anything", "what should we cover for X", "help me think through the tests for Y", or when the user describes a feature and hasn't mentioned implementation yet. Also trigger when the user asks Claude to implement something non-trivial and no test plan exists — propose running this protocol first before jumping to tdd-design.
Outline an initial behavioral test plan using Given/When/Then for a target feature before any code is written.
High-intent search queries and answers about installing and using this skill.
Defining test scenarios before coding involves creating a structured behavioral contract using Given/When/Then phrasing to outline unit boundaries, edge cases, and acceptance criteria for early-stage feature design.
A behavioral contract is a collaborative specification protocol outlining the expected behavior of a software unit before implementation. It uses plain language test cases to align teams on acceptance criteria and edge-case coverage.
Writing Given/When/Then test cases for feature planning requires outlining initial conditions, actions, and expected outcomes in plain language to drive downstream test-driven development and clarify unit boundaries.
You should plan edge-case coverage before test-driven development when implementing non-trivial features, ensuring a shared RFC-style spec exists to align on acceptance criteria and behavioral contracts during collaborative sessions.
Yes, test planning works before any code is written by proposing structured test scenarios in plain language, encouraging early clarification of unit boundaries and iterative discussion phases to align on the behavioral contract.
The best way to align on acceptance criteria is using a collaborative specification protocol that proposes structured test scenarios and an artifact-ready outline, driving iterative discussion before jumping to implementation.
tellbomConvert natural language feature descriptions into structured specifications with acceptance criteria.
NSObjectsDefine behavioral requirements with GIVEN/WHEN/THEN scenarios and edge cases.
maksutovicTriage bugs and guide teams through diagnosis, discussion, and specification before implementation.
rhussGenerate implementation plans and TDD cycles from validated specifications.
