test-design

Extracts testable behaviors from features and routes them through method selection and verification stages.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hakkadaikon/hymme --skill test-design-hakkadaikon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-design
Source: https://github.com/Hakkadaikon/hymme/tree/main/skills/test-design
Command: npx skills add https://github.com/Hakkadaikon/hymme --skill test-design-hakkadaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often write tests ad hoc, missing edge cases and producing brittle or flaky suites. This Skill acts as a router for test design: it exhaustively extracts the behaviors worth testing from a feature, module, API, or PR diff, assigns concrete test methods to each, and bridges the results into implementation and regression. ## Core Features & Use Cases - Behavior Extraction (test-extract): Enumerates all testable behaviors into a numbered T-ID ledger, and for reviews reads existing tests bidirectionally against the ledger. - Method Selection (test-catalog): Assigns each behavior a technique from a catalog of 40 test methods (equivalence partitioning, state transition, mutation testing, property-based testing, and more), opening only the relevant reference. - Verification & Handoff (test-verify): Bridges to TDD implementers, enforces execution gates (coverage back-tracing, flaky checks, mutation), and fixes tests into CI as regression. - Use Case: Before planning a new API endpoint, run the pipeline to produce a complete T-ID ledger with assigned methods, then hand it to the implementer so every failing test traces back to a designed behavior. ## Quick Start Ask the assistant to design the test cases for a specific feature, module, or PR diff you are working on.

Frequently Asked Questions about test-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design test cases before writing code?

Run the extraction stage to enumerate all testable behaviors of the target into a numbered T-ID ledger, then assign each behavior a method from the test catalog. The resulting ledger feeds directly into TDD tasks so every failing test traces to a designed behavior.

How to review existing tests for missing coverage?

Use the extraction stage in review mode: it lists the behaviors that should be tested and maps existing tests against them bidirectionally. Gaps, unjustified priority drops, and missing entries are flagged before you proceed.

What test design techniques are covered?

The catalog indexes 40 techniques including equivalence partitioning, boundary values, state transition testing, property-based testing, mutation testing, golden tests, test doubles, and pairwise testing. Only the reference for the assigned method is opened.

Does this replace TDD or test-driven-development workflows?

No. It covers what to test (extraction, method selection, verification), while the Red-Green-Refactor cycle itself is delegated to a separate TDD skill executed by the implementer. The two are designed to work together.

When should I not use a formal test design process?

Skip it for trivial one-line changes, configuration values, or small edits where the method is obvious, following the YAGNI principle. Single-method questions can also be answered by consulting the catalog index alone without creating a ledger.