wicked-testing

Run the 3-agent acceptance pipeline (Writer → Executor → Reviewer) on a scenario file

Author scenarios and generate test code — dispatches the authoring skill

Run tests and capture evidence — dispatches the execution skill

Query the ledger — stats, reports, flake detection, coverage gaps

Generate a test strategy — dispatches the plan skill's 4-way router (strategist / risk / testability / AC-quality)

Follows structured wicked-testing test plans step-by-step, collecting evidence artifacts. Executes and captures only — does not judge or grade pass/fail. Writes evidence files to .wicked-testing/evidence/{run-id}/. Use when: acceptance test execution, evidence collection, test plan execution <example> Context: Test plan is ready and needs to be executed step by step. user: "Execute the acceptance test plan for the file upload feature." <commentary>Use acceptance-test-executor for mechanical step execution and evidence capture without judging results.</commentary> </example>

Evaluates evidence artifacts against test plan assertions independently. CRITICAL ISOLATION: Receives ONLY evidence file paths. Never sees execution context. Catches semantic bugs that self-grading misses. Use when: acceptance test review, evidence evaluation, test verdict <example> Context: Executor produced evidence and it needs independent evaluation. user: "Review the evidence from the file upload acceptance tests and render a verdict." <commentary>Use acceptance-test-reviewer for independent, unbiased verdict on test evidence.</commentary> </example>

Reads wicked-testing acceptance scenarios and produces structured, evidence-gated test plans. Transforms qualitative criteria into concrete, verifiable artifact requirements. Use when: acceptance testing, test plan generation, scenario verification design <example> Context: New feature scenario needs a structured test plan. user: "Write an acceptance test plan for the 'user can export data as CSV' scenario." <commentary>Use acceptance-test-writer to produce structured, evidence-gated test plans from scenarios.</commentary> </example>

Static code analysis for testability, quality, and maintainability. Reviews code structure, identifies test-coverage gaps, and flags risky areas. Use when: static analysis, code-quality metrics, testability assessment, maintainability review, coverage-gap identification. Runs on arbitrary source code, anytime — does not require a spec or an active build phase. NOT THIS WHEN: - Reviewing acceptance criteria for SMART+T (pre-code, no implementation yet) — use `requirements-quality-analyst` - Judging whether the implementation matches a spec (post-code divergence detection) — use `semantic-reviewer` - Rendering a full acceptance verdict (writer + reviewer + executor pipeline) — use `/wicked-testing:acceptance`

API contract testing specialist. Designs and reviews consumer-driven contracts, Pact-style tests, OpenAPI contract verification, schema versioning, and breaking-change detection across service boundaries. Use when: API contract tests, CDC, Pact, OpenAPI verification, schema versioning, breaking-change detection, provider/consumer negotiation.

Evidence-gated acceptance testing with three-agent separation of concerns. Writer designs test plans, Executor collects artifacts, Reviewer evaluates independently. Eliminates false positives from self-grading. Use when: "acceptance test", "verify it works", "did it pass", "run acceptance", "test this scenario", "acceptance criteria", "validate the feature", "/wicked-testing:acceptance"

Tier-1 orchestrator for producing tests. Writes scenario files, generates test code (unit / integration / E2E), creates fixtures and test data. The "make me tests" skill. Use when: "write tests", "generate test code", "author scenarios", "create a scenario file", "add fixtures", "test data setup", "automate this scenario".

Tier-1 orchestrator for running tests and capturing evidence. Executes scenarios, invokes framework runners, collects artifacts, and writes the run + verdict to the ledger. Use when: "run the test", "execute this scenario", "run the suite", "acceptance test this", "capture evidence", "prove it works".

Tier-1 orchestrator for reading the ledger. Stats, reports, flake detection, coverage gaps, historical queries. Never writes — only reads. Use when: "has this passed recently", "flake rate", "show me the last N runs", "coverage gaps", "generate a report", "stats", "exploratory session".

Tier-1 orchestrator for test planning. Covers test strategy, risk, testability review, and requirements quality. Dispatches specialist agents based on what the target needs. Use when: "what should I test", "test strategy", "test plan", "risk matrix", "is this testable", "are these requirements testable", "coverage strategy", "shift-left testing".

1 hook across 1 event