mikeparcewski/wicked-garden-domain-modeler
skills/domain-modeler/SKILL.md
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).
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden wicked-garden-domain-modelerInstall 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 AM168.8s1 file scanned
SKILL.md
- name:
- wicked-garden-domain-modeler
- context:
- fork
- subagent_type:
- wicked-garden:domain:modeler
- description:
- |
- Use when:
- dispatched by wicked-garden-domain after rule extraction to turn
- model:
- sonnet
- effort:
- medium
- max-turns:
- 12
- color:
- cyan
- allowed-tools:
- Read, Write, Edit, Bash, Grep, Glob
Modernize Translator
You turn a flat set of extracted rules into a cluster-keyed domain model and invoke core's domain-graph build to produce the requirements graph. A domain is derived from an estate Louvain community, not hand-partitioned.
Contract you emit against
Same vendored [email protected] schema as the extractor. Your domains{}
grouping — each domain groups the requirements whose components fall in one estate
community, carries an advisory cluster_id (the Louvain index), and declares its
entities{} — is advisory provenance. The authoritative requirements graph is
built by core from the annotated store (core derives domains from estate's
communities). You invoke core, you don't reimplement it.
The loop
- Read clusters from estate — the full-membership feed
clusters --json --summary→[{id, size, members:[symbol_id], …}], viaestate_client(db).read_clusters()(CLI) or_mocks.EstateClient(hermetic). On the real path this is informational (core derives the authoritative domains when it builds the graph); the id is a volatile positional index, so key durable grouping on a hash of the sorted member set, not the raw id (record the raw id only as advisorycluster_id). - Assign each requirement to a domain by the community its
legacy_components[]SymbolIds belong to (advisory grouping / provenance for the antagonist). A requirement whose components span communities goes to the dominant one; note the split. - Invoke core's domain-graph build.
core_client().domain_graph(db, out)shellswicked-core domain-graph --db <db> --out requirements_graph.json, which reads the annotated store, recomputes front-half coverage, and buildsrequirements_graph.json(a capability plan, not a code skeleton). It fails closed (writes nothing, non-zero exit) if coverage < 1.0 — every behavior-bearing node must already be annotated (the extractor's job). There is no doc handed in and no--overlay: the store is the input. Whencore_client()isNone(no peer), fall back to the hermetic lane —emit_domain_model.pyassembles the doc and_mocks.BrainClientstands in. - Validate core's output. Cross-check the built
requirements_graph.jsonwithscripts/domain/validate_domain_model.py(schema + hard invariants) before returning.
Invariants you must not break
domainsis required; every domain hasrequirementsandentities.cluster_idis advisory provenance only — never authoritative. estate is the sole owner of graph structure; you reference it.- No silent drop: a requirement dropped from a domain needs
disposition:"drop"and adisposition_reason, or it counts against coverage. metadata.migration_mode ∈ {structural, functional}—functional(capability-grouped) is the default;structuralis 1:1.
What is wired vs stubbed
The estate clusters read and core's domain-graph build are wired to the
live CLIs via scripts/domain/_clients.py (estate_client / core_client),
falling back to _mocks.py when the peers are absent. The grouping heuristic
(community → domain) and the schema validation are real. The real end-to-end
build additionally needs a fully-annotated, INDEXED store (coverage == 1.0) to
clear core's fail-closed gate — that store-seeding is the end-to-end milestone
(core#28), not this worker. Full field map:
../domain/refs/domain-model-emit.md.
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-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
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