mikeparcewski/acceptance-testing
skills/acceptance-testing/SKILL.md
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: "run acceptance tests", "verify it works", "did it pass", "test this scenario", "acceptance criteria", "validate the feature"
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden acceptance-testingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 6:07 AM16.1s4 files scanned
SKILL.md
- name:
- acceptance-testing
- description:
- |
- Use when:
- run acceptance tests", "verify it works", "did it pass",
- context:
- fork
- agent:
- test-designer
- status:
- deprecated
Acceptance Testing
Deprecated: This skill was replaced in v6 by
/wicked-garden:qe:acceptance(three-agent pipeline) and thetest-designeragent. Use those instead.
Three-agent pipeline that separates test writing, execution, and review for higher-fidelity acceptance testing.
The Problem with Self-Grading
When the same agent executes and grades tests, it pattern-matches "something happened" as success:
- Command produced output → "PASS" (but output was wrong)
- File was created → "PASS" (but contents are incorrect)
- No errors → "PASS" (but the feature didn't activate)
Result: 80%+ false positive rate on qualitative criteria.
Three-Agent Architecture
Writer ──→ Test Plan ──→ Executor ──→ Evidence ──→ Reviewer ──→ Verdict
| Agent | Role | What it catches | |-------|------|-----------------| | Writer | Reads scenario + implementation code → structured test plan with evidence gates | Specification bugs — scenario expects X, code does Y | | Executor | Follows plan step-by-step → collects artifacts, no judgment | Runtime bugs — crashes, missing files, timeouts | | Reviewer | Evaluates cold evidence against assertions | Semantic bugs — everything ran but output is wrong |
Quick Start
# Full pipeline on a scenario
/wicked-garden:qe:acceptance path/to/scenario.md
# Generate test plan only (inspect before running)
/wicked-garden:qe:acceptance scenario.md --phase write
# Run all scenarios for a plugin
/wicked-garden:qe:acceptance wicked-garden:mem --all
Scenario Formats Supported
- Plugin acceptance scenarios — wicked-garden
scenarios/*.mdformat - User stories with acceptance criteria — Given/When/Then format
- E2E scenarios — wicked-scenarios CLI-based format
- Custom acceptance criteria — any structured test description
Key Concepts
Evidence-Gated Steps
Every step in the test plan requires the executor to produce specific artifacts. No evidence = no verdict (INCONCLUSIVE, not auto-PASS).
Assertion Types
| Type | Example | Auto-evaluable |
|------|---------|----------------|
| CONTAINS | stdout contains "success" | Yes |
| MATCHES | output matches score: \d+ | Yes |
| EXISTS | file at path exists | Yes |
| JSON_PATH | $.status equals "ok" | Yes |
| HUMAN_REVIEW | "Is output actionable?" | No — flagged for human |
Failure Causes
| Cause | Who fixes |
|-------|-----------|
| IMPLEMENTATION_BUG | Developer |
| SPECIFICATION_BUG | Scenario author |
| ENVIRONMENT_ISSUE | DevOps/setup |
| TEST_DESIGN_ISSUE | Test writer |
Agents
| Agent | Purpose | |-------|---------| | acceptance-test-writer | Transforms scenarios into evidence-gated test plans | | acceptance-test-executor | Executes plans, collects artifacts, no judgment | | acceptance-test-reviewer | Evaluates evidence against assertions independently |
Detailed References
- Test Plan Format — Structure, fields, and examples for test plans
- Evidence Collection — How to capture and structure evidence
- Evidence Validation — How to evaluate, verify, and manage evidence
Evidence Package Output
When running within a crew test phase, the executor compiles an evidence package at phases/test/evidence/report.md containing:
- Screenshots: Captured during E2E/visual test execution
- Execution traces: Step-by-step log with timestamps and durations
- Spec comparison: Acceptance criteria mapped to test results
The review phase consumes this package for informed sign-off decisions. Pass/fail alone is insufficient — reviewers need visual proof and execution context.
Use /wicked-garden:qe:report to generate structured evidence from scenario execution results.
Integration
- wicked-crew: Evidence-gated quality gates during delivery phases. Test phase compiles evidence package; review phase evaluates it.
- wicked-scenarios: Executor delegates E2E CLI steps to
/wicked-garden:qe:run --jsonfor machine-readable execution artifacts. Writer understands E2E scenario format natively. Falls back to inline bash execution when scenarios plugin is not installed. - /wg-test: Delegates to
/wicked-garden:qe:acceptanceas the single acceptance pipeline. QE owns Writer/Executor/Reviewer end-to-end. - Any project: Works with custom acceptance criteria, not just wicked-garden plugins
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026