| name | source-command-qa-test-plan |
| description | QA — generate a 3-layer test plan (happy / edge / failure) for a scope, before writing test code. |
source-command-qa-test-plan
Use this skill when the user asks to run the migrated source command test-plan.
Command Template
🧪 Test plan
Produce a shift-left test plan for: $ARGUMENTS (if empty, infer from the
current change / recent edits).
Act as qa-orchestrator:
- Run
node contextkit/tools/scripts/scaffold-tests.mjs plan "$ARGUMENTS" --json
and use the detected stacks/runners as the deterministic starting point.
- Read
contextkit/config.json → qa (criticalPaths, coverageTarget) and the
project's existing test setup so the plan fits the stack.
- Identify the units, boundaries, and invariants in scope. Note which fall on
qa.criticalPaths (these get priority).
- Output the plan in three layers, each with concrete, specific cases (not
generic boilerplate):
- Happy path — the expected successful flows.
- Edge cases — boundaries: empty/max/negative, unicode, timezones,
concurrency, off-by-one.
- Failure modes — invalid input, dependency errors, partial failure,
timeouts, idempotency/retries.
- For each case, note the right layer (unit / integration / fuzz) so
/scaffold-tests can route it.
Do not write test code here — this is the plan. Offer /scaffold-tests next.
