Requires: pip install openpyxl — this skill's scripts import openpyxl.

Generating Test Cases

Turn a feature, change, or fixed bug into a structured, evidence-grounded test-case suite, then render it to whatever destination the user wants. Coverage is derived once from the sources of truth; the output format is a late, swappable step.

The whole skill rests on one discipline you must not skip:

🔒 Iron Law — No test case, no expected value, no test datum without a cited source — and no value left as a category when the test needs an instance. Every row points to where it came from: a doc, source code (file:line), git, or the live system. If a value can't be found in a real source, you do not write it — you mark it TBD (needs confirmation) and ask. Guessing is a defect, not a shortcut.

Violating the letter of this rule is violating its spirit. Two failure modes break it, not one:

• Fabrication — a plausible-but-unsourced value. Worse than blank: it looks verified and isn't.
• Under-specification — a value or precondition filled with the spec's class instead of a concrete instance (an email with ≥1 attachment, a valid user, some cargo record). It is "sourced" — you copied the spec — so it slips the source check, carries no hedge word, and can even cite an Evidence cell. But it's untestable. A category is not a value. Resolve it to the real instance (Step 2) or mark TBD (needs confirmation) and ask — never leave the abstraction.

When to invoke