mikeparcewski/test-task-factory
skills/crew/test-task-factory/SKILL.md
Generates test task creation parameters from a detected change type and implementation task subject. Routes to the correct test type (visual/endpoint) and produces TaskCreate-ready subjects, descriptions, and metadata. Use when: creating test tasks after change-type detection, QE task generation, "test task factory", "create test tasks", "generate QE tasks", or after change-type-detector classifies files as ui/api/both.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden test-task-factoryInstall 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: May 7, 2026, 6:25 AM214.9s3 files scanned
SKILL.md
- name:
- test-task-factory
- description:
- |
- Use when:
- creating test tasks after change-type detection, QE task generation,
- phase_relevance:
- ["*"]
- archetype_relevance:
- ["*"]
Test Task Factory Skill
Generate test task parameters from a change type. The output is ready for TaskCreate — no further processing needed.
Quick Reference
| Input | Test Tasks Created |
|-------|--------------------|
| ui | 1 task — visual category |
| api | 1 task — endpoint category |
| both | 2 tasks — visual + endpoint |
| unknown | 0 tasks — emit warning, no tasks |
Algorithm: Step by Step
Step 1 — Strip phase prefix from impl subject
Remove leading phase label and optional project name from the implementation
task subject to get the clean impl_description.
Pattern to strip: ^(build|clarify|design|ideate|test-strategy|test|review|implement)\s*:\s*
(case-insensitive)
Then strip project prefix: If the result matches {project-name} - {description},
take only the part after -.
Examples:
"Build: my-project - Implement login form"→"Implement login form""Build: Implement login form"→"Implement login form""Implement login form"→"Implement login form"(unchanged)
Step 2 — Generate safe filename fragment
Convert impl_description to lowercase, replace non-alphanumeric runs with -,
strip leading/trailing dashes, cap at 50 characters. Used in screenshot path
templates in descriptions.
Step 3 — Route by change type
change_type == "unknown" → return empty test_tasks list + warning (see below)
change_type == "ui" → create 1 task using ui template
change_type == "api" → create 1 task using api template
change_type == "both" → create 2 tasks: ui template first, then api template
unrecognized value → return empty test_tasks list + warning
Step 4 — Construct subject
Test: {project} - {impl_description} ({test_category})
Where test_category is:
visualfor ui tasksendpointfor api tasks
Step 5 — Fill description template
See Test Task Templates for full template text per test type.
Step 6 — Assemble metadata
{
"initiative": "{project}",
"priority": "P1",
"assigned_to": "acceptance-test-executor",
"test_type": "{ui|api}",
"evidence_required": [...],
"evidence_optional": [...],
"impl_subject": "{original impl_subject}"
}
See Test Evidence Taxonomy for evidence field values per test type.
Output Format
{
"test_tasks": [
{
"subject": "Test: my-project - Implement login form (visual)",
"description": "...",
"metadata": { ... }
}
]
}
For unknown or unrecognized change types:
{
"test_tasks": [],
"suppressed": true,
"warning": "change_type is 'unknown' — no test tasks created for '...'. ..."
}
Warning Text (unknown change type)
change_type is 'unknown' — no test tasks created for '{impl_description}'. No UI or API files were detected. If this task touches UI or API code, re-run change-type detection with the correct file paths.
Warning Text (unrecognized change type)
Unrecognized change_type '{value}' — no test tasks created.
Usage Example
Input:
change_type:"both"impl_subject:"Build: checkout - Integrate payment flow"project:"checkout"
Produces impl_description = "Integrate payment flow", then two tasks:
"Test: checkout - Integrate payment flow (visual)"with ui template"Test: checkout - Integrate payment flow (endpoint)"with api template
See Test Task Templates for full template content and Test Evidence Taxonomy for evidence field values.
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