test-design

To derive testable acceptance criteria, you need structured guidelines that define exactly what constitutes 'done and correct' functionality. This skill assists by formulating clear criteria, ensuring your features have testable boundaries from the start.

Identifying edge cases and boundary conditions requires a comprehensive testing strategy that enumerates various scenarios and breaking cases. This skill formulates a complete set of test cases to cover these specific error modes and boundary limits.

Auditing test coverage gaps involves manual review to ensure no significant testable aspect is overlooked. This skill provides guidelines for reviewing and correcting gaps, making it ideal for auditing tests at the end of a TDD development cycle.

Yes, you can use this approach to design initial test cases before implementation. When implementing Test-Driven Development, this skill helps design upfront test cases and formulate acceptance criteria to guide your coding.

No specific testing frameworks or dependencies are required. This skill focuses on internal design and reasoning for test planning, providing manual review and guidance rather than relying on external components or libraries.

Your test suite misses critical error modes due to coverage gaps in the testing strategy. You can fix this by using structured guidelines to audit coverage, identify overlooked testable aspects, and formulate comprehensive test cases for error modes.