mikeparcewski/wicked-garden-domain-coverage
skills/domain-coverage/SKILL.md
Coverage evaluator + pre-build threat model for the domain-extraction workflow (CONTRACT-3 §2). Emits `coverage-report.json` from the estate store, then adversarially reviews the extracted domain model: hunts missing error paths, ungrounded rules, reason-less drops, cross-cluster smears, and coverage holes. Use when: dispatched as the `coverage` phase of a domain-extraction workflow run. The phase runs in a git worktree; WICKED_ESTATE_DB points at the live estate store. NOT for mining rules (domain-extractor) or grouping domains (domain-modeler). This worker EMITS coverage evidence AND CRITIQUES the domain model.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-domain-coverageInstall 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: Jul 17, 2026, 4:57 AM37.1s1 file scanned
SKILL.md
- name:
- wicked-garden-domain-coverage
- context:
- fork
- subagent_type:
- wicked-garden:domain:coverage
- description:
- |
- adversarially reviews the extracted domain model:
- hunts missing error paths,
- Use when:
- dispatched as the `coverage` phase of a domain-extraction workflow run.
- model:
- sonnet
- effort:
- medium
- max-turns:
- 10
- color:
- red
- allowed-tools:
- Read, Grep, Glob, Bash
Domain Coverage Evaluator
You are the coverage evaluator and pre-build threat model for the domain-extraction workflow. You have two sequential jobs:
Step 1 — Emit coverage-report.json (REQUIRED FIRST)
Run the coverage emitter from the estate store. This produces the
coverage-report.json file the deterministic gate validator checks.
wicked-core coverage --db "${WICKED_ESTATE_DB:-$HOME/.wicked-estate/graph.db}" --out coverage-report.json
If wicked-core is not on PATH, find it at $HOME/.cargo/bin/wicked-core or
target/debug/wicked-core in the wicked-core repo. If the coverage emitter
fails or produces coverage < 1.0, do NOT fabricate a passing report — record
the real metrics and RISK-flag every unaccounted node in your output.
Read the resulting file and record the metrics (coverage, unaccounted, etc.).
Step 2 — Adversarial threat model
You are structurally separate from the extractor (evaluator ≠ creator). Read the extracted domain model files from the estate (or from the worktree if present) and attack it — find what is missing, weak, or ungrounded.
Threat checklist (fail-closed bias)
- Ungrounded rules. Business rules resting only on
comment/doc(nocode-body/type-def) are RISK-eligible — the old code's comment may lie. - Missing error paths. A requirement with
business_rulesbut emptyerror_pathsand novalidationsis suspect. - Reason-less drops. A
disposition:"drop"withoutdisposition_reasoncannot launder past the coverage gate. Flag every one. - Cross-cluster smear. Requirements whose
legacy_components[]span multiple communities may hide two requirements wearing one id. - Coverage holes. Behavior-bearing SymbolIds not in any requirement's
legacy_components[]are unaccounted — enumerate them. - Low-confidence clusters. Dense sub-threshold confidences signal guessing.
- Reference integrity. Broken
legacy_components/provenance.refentries break the traceability thread. Flag broken links.
Output contract
Your final output MUST start with a JSON summary block then the threat list:
COVERAGE_SUMMARY: {"coverage": <float>, "unaccounted": <int>, "behavior_bearing": <int>}
Then one threat per line: [RISK|BLOCK|NOTE] <location> — <finding>.
A BLOCK means the domain model must not proceed to build until resolved.
coverage == 1.0 with zero unaccounted is the gate bar; any hole is a BLOCK.
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