Menú
QA — materialize tests for the given files, routing each slice to the right specialist.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | source-command-qa-scaffold-tests |
| description | QA — materialize tests for the given files, routing each slice to the right specialist. |
Use this skill when the user asks to run the migrated source command scaffold-tests.
Materialize tests for: $ARGUMENTS
Act as qa-orchestrator and route work to the specialists (fan out in parallel for independent slices via the Agent tool when available):
qa.criticalPaths./visual-test).Before dispatch, run:
node contextkit/tools/scripts/scaffold-tests.mjs plan "$ARGUMENTS" --json
Use that stack-aware matrix to decide which specialists should receive which slices. If the project has no test harness yet, run a dry-run first:
node contextkit/tools/scripts/scaffold-tests.mjs scaffold "$ARGUMENTS"
Only create starter harness files with explicit write intent:
node contextkit/tools/scripts/scaffold-tests.mjs scaffold "$ARGUMENTS" --write
Dispatches inherit each specialist's frontmatter model: tier (ADR-0052 —
qa-unit/qa-integration run on the fast tier; their output is guarded by rule 4
below). If a specialist's output fails the suite twice, re-dispatch exactly once,
one tier up, and report the escalation.
Rules:
/test-plan if one
exists).If sub-agents aren't available in this environment, write the tests yourself but keep the unit / integration / fuzz separation explicit.
Domain Engineering diagnostic — shows what the classifier decides for an objective (CMIS/DAS/profile/skills/mode). Observation-only; never mutates or blocks.
Business-driven methodology entry point — classify (intake), create/advance an Operation or Business work context, and drive the intake → operation → nested-workflow flow. Host-neutral; dry-run by default.
Workflow Navigator — shows the current phase, deliverables, and next commands for an ADR-0057 workflow. Read-only; never mutates state.
Start a focused session on one objective — locks scope, blocks opportunistic refactors.
Deterministic QA gate (ADR-0055) — run the project suite; green + complete acceptance criteria ⇒ qa-approve testing cards into conclusion; red ⇒ report (and qa-reject only attributable failures).
L6 — autonomous feature pipeline. Drives the full squad: design → implement → review → test → log. Checkpoints can be manual or automatic.