From autoworker
Execute ONE test level (L1/L2/L3/L4) from subtask verification plan. Only run tests, do not record results. Called by autoworker:dispatch with level argument. Ends by calling autoworker:checkpoint.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autoworker:testThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Called by autoworker:dispatch with a target level argument. Does one thing: execute all test items for that layer from the subtask verification plan.
Called by autoworker:dispatch with a target level argument. Does one thing: execute all test items for that layer from the subtask verification plan.
autoworker:test L2) → use that levelGlob `subtask_*.md` (exclude subtask_template.md) →
0 found → stop, prompt to create subtask
1 found → use directly (backward compatible)
multiple → grep `status:` to filter:
- Files without status field treated as active (backward compatible)
- Exactly 1 active → use it
- 0 active → list all files + status, prompt user to choose
- >1 active → report anomaly
→ Read → extract all verification items for the target level
Each item contains:
For each verification item in the layer:
run_in_background=true, then TaskOutput to wait for results)Pass determination hard standard:
When a test fails:
When all pass:
L<N> tests passed:
- <item 1>: <actual output summary> PASS
- <item 2>: <actual output summary> PASS
→ Invoking autoworker:checkpoint
After outputting the summary, immediately invoke autoworker:checkpoint. Do not wait for user instructions, do nothing else.
npx claudepluginhub phj128/autoworker --plugin autoworkerComplete subtask verification plan: upstream traceability table + L1-L4 test plan + self-check. Call after autoworker:subtask-init. Makes subtask ready for code implementation.
Freezes acceptance criteria before building, then uses independent agents to verify each criterion against the plan. Prevents self-verification bias and ensures build-to-spec traceability.
Verifies completed work with a 3-tier evidence-based process. Validates tests, linting, types, builds exist and pass, plus deep audit for milestones and PRs. Enforces no completion claims without fresh evidence.