wicked-garden-domain-extractor

Stars8

Forks2

UpdatedJuly 15, 2026 at 06:05

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).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

mikeparcewski

mikeparcewski/wicked-garden

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	wicked-garden-domain-extractor
context	fork
subagent_type	wicked-garden:domain:extractor
description	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).
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 domain-model@1.0.0 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 Bash call):
```
python3 scripts/domain/extract_loop.py --db "<estate-store>" --time-budget 780
```
It seeds its worklist from wicked-core coverage's own unaccounted_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 writes annotate + 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 with unaccounted > 0, re-invoke it to resume — the shrunk worklist re-seeds, so work never repeats. Stop when unaccounted hits 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-coverage phase (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), grounded provenance{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 (default claude -p). Set-but-empty is the kill-switch → the harness's --dry-run deterministic stub only.

Hard invariants (fail-closed — enforced by the harness + validator)

Every requirement has business_rules with minItems 1.
Every business rule: numeric confidence ∈ [0,1] and provenance{source, ref, source_kinds}.
legacy_components[] is non-null, never dropped — the SymbolIds the requirement covers.
disposition ∈ {keep, modify, drop, new}; a drop needs a disposition_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.py seam.

More from this repository

same repository

wicked-garden-archetype

mikeparcewski/wicked-garden

v11 work-shape archetype runner. When a prompt has been routed to one of the archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate, modernize), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or a direct per-archetype ask — "triage this prompt", "review this PR / artifact", "build this feature", "decide between these options", "explore this problem", "handle this incident", "run this migration", "modernize / port this legacy app", "ship this release", "write acceptance criteria" (invoke with archetype=<name> plus the user's args — see the Direct invocation table).

2026-07-218

wicked-garden-engineering-conformance-reviewer

mikeparcewski/wicked-garden

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.

2026-07-168

wicked-garden-domain-coverage

mikeparcewski/wicked-garden

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.

2026-07-168

wicked-garden-core

mikeparcewski/wicked-garden

Core utility surface for the wicked-garden plugin: help/overview, first-run setup + codebase onboarding, the wicked-* peer installer, selective state reset, the where-am-i path manifest, and structured issue filing. Use when: "wicked-garden help", "show wicked-garden commands", "what can wicked-garden do", "set up wicked-garden", "setup", "--reconfigure", "onboard this codebase", "install wicked tools", "add peers", "install layers", "reset wicked-garden", "clear state", "--list-projects", "where am I", "path manifest", "report issue", "file a bug", "--list-unfiled", or any former /wicked-garden:{help|setup|install|reset| where-am-i|report-issue} invocation.

2026-07-158

wicked-garden-domain-modeler

mikeparcewski/wicked-garden

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).

2026-07-158

wicked-garden-domain

mikeparcewski/wicked-garden

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

2026-07-158

name	wicked-garden-domain-extractor
context	fork
subagent_type	wicked-garden:domain:extractor
description	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).
model	sonnet
effort	medium
max-turns	12
color	green
allowed-tools	Read, Write, Edit, Bash, Grep, Glob

Domain Extractor

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 Bash call):
```
python3 scripts/domain/extract_loop.py --db "<estate-store>" --time-budget 780
```
It seeds its worklist from wicked-core coverage's own unaccounted_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 writes annotate + 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 with unaccounted > 0, re-invoke it to resume — the shrunk worklist re-seeds, so work never repeats. Stop when unaccounted hits 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-coverage phase (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), grounded provenance{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 (default claude -p). Set-but-empty is the kill-switch → the harness's --dry-run deterministic stub only.

Hard invariants (fail-closed — enforced by the harness + validator)

Every requirement has business_rules with minItems 1.
Every business rule: numeric confidence ∈ [0,1] and provenance{source, ref, source_kinds}.
legacy_components[] is non-null, never dropped — the SymbolIds the requirement covers.
disposition ∈ {keep, modify, drop, new}; a drop needs a disposition_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.py seam.