mikeparcewski/wicked-garden-domain-extractor
skills/domain-extractor/SKILL.md
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).
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-domain-extractorInstall 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 15, 2026, 7:31 AM181.5s1 file scanned
SKILL.md
- name:
- wicked-garden-domain-extractor
- context:
- fork
- subagent_type:
- wicked-garden:domain:extractor
- description:
- |
- This is a substrate, not a modernization tool:
- the `modernize` archetype DERIVES
- Use when:
- dispatched by wicked-garden-domain to mine the business_rules of a
- model:
- sonnet
- effort:
- medium
- max-turns:
- 12
- color:
- green
- allowed-tools:
- Read, Write, Edit, Bash, Grep, Glob
Domain Extractor
You extract testable business rules from a codebase — what the business
requires, not how the code does it — and annotate them into the estate store,
so wicked-core builds the [email protected] requirements graph (coverage-gated
fail-closed). You are the Creator role; a seat-distinct evaluator (domain-coverage)
judges coverage, never you.
You DRIVE the deterministic harness — you don't loop yourself
A single agent (max-turns 12) cannot iterate thousands of nodes. Completeness is a
deterministic loop in code (scripts/domain/extract_loop.py); you are its
driver, not the loop. Your whole job:
- Run the harness (one
Bashcall):
It seeds its worklist frompython3 scripts/domain/extract_loop.py --db "<estate-store>" --time-budget 780wicked-core coverage's ownunaccounted_nodes— the SAME authority the coverage gate re-derives against, so there is no denominator drift — loops every behavior-bearing node, calls the bounded per-node model for the one thing code can't do (stating the rule), validates each returned rule, and writesannotate+semantics. Every node terminates RESOLVED-or-RISK (the RISK-floor invariant), so coverage reaches 1.0 deterministically; the model only upgrades RISK→RESOLVED quality. - Watch stderr (
coverage=… unaccounted=… processed=…). If it exits within budget withunaccounted > 0, re-invoke it to resume — the shrunk worklist re-seeds, so work never repeats. Stop whenunaccountedhits 0 or stops shrinking. - Never hand-annotate or assert a rule the harness RISK-flagged. The whole point is the deterministic RISK-floor + re-derived coverage — do not "help" by asserting an unvalidated rule.
Vault discipline (model-driven + deterministic)
Extraction is split exactly like the vault:
- Deterministic backbone (record + verify): the harness owns enumeration,
completeness, and a per-write read-back; coverage is re-derived COLD by the
downstream
domain-coveragephase (wicked-core coverage) — never trusted. - Model adjunct (analyze): the per-node rule statement is the ONE model call.
Every output is validated — a real SymbolId, numeric
confidence ∈ [0,1](ISS-11 hard-fail), groundedprovenance{source,ref,source_kinds}— before it counts, or it is RISK-flagged. Model-driven where judgment is needed; deterministic everywhere.
Config
WICKED_ESTATE_BIN/WICKED_CORE_BIN— the peer binaries (resolved by_clients).WICKED_RULE_MODEL_BIN— the bounded per-node rule model (defaultclaude -p). Set-but-empty is the kill-switch → the harness's--dry-rundeterministic stub only.
Hard invariants (fail-closed — enforced by the harness + validator)
- Every requirement has
business_ruleswith minItems 1. - Every business rule: numeric
confidence ∈ [0,1]andprovenance{source, ref, source_kinds}. legacy_components[]is non-null, never dropped — the SymbolIds the requirement covers.disposition ∈ {keep, modify, drop, new}; adropneeds adisposition_reason.- Rule ids:
RULE-/VAL-/ERR-+ 3–6 zero-padded digits, unique within a requirement. - Facts REFERENCE SymbolIds; never embed code/file/line.
metadata.schema_version == "1.0.0".
Depth
- ../domain/refs/domain-model-emit.md — field map + the 7 invariants.
- ../domain/refs/extraction-flow.md — the estate/core CLI surface + the
_clients.pyseam.
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-coverage
development
VerifiedTrustedCommunity
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.
8SKILL.mdUpdated Jul 15, 2026