wicked-garden-domain-modeler
Skill9 starsChanged 7 months agoMITView on GitHub
Domain-graph 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 below the configured minimum — and builds the requirements graph) — then validates core's output against the vendored schema.
In this repository142 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- plugin-json-schemaSkill
- readme-style-guideSkill
- releaseSkill
- scaffoldSkill
- wicked-garden-agentic-agentic-patternsSkill
- wicked-garden-agentic-architectSkill
- wicked-garden-agentic-context-engineeringSkill
- wicked-garden-agentic-frameworksSkill
- wicked-garden-agentic-performance-analystSkill
- wicked-garden-agentic-review-methodologySkill
- wicked-garden-agentic-safety-reviewerSkill
- wicked-garden-agenticSkill
- wicked-garden-agentic-trust-and-safetySkill
- wicked-garden-appsSkill
- wicked-garden-archetypeSkill
- wicked-garden-build-guideSkill
- wicked-garden-classifySkill
- wicked-garden-coreSkill
- wicked-garden-data-engineerSkill
- wicked-garden-dataSkill
- wicked-garden-deliberateSkill
- wicked-garden-demoSkill
- wicked-garden-domain-coverageSkill
- wicked-garden-domain-extractorSkill
- wicked-garden-domainSkill
- wicked-garden-draftSkill
- wicked-garden-editor-scaffoldSkill
- wicked-garden-engineering-api-documentarianSkill
- wicked-garden-engineering-architectureSkill
- wicked-garden-engineering-backendSkill
- wicked-garden-engineering-debuggingSkill
- wicked-garden-engineering-docsSkill
- wicked-garden-engineering-frontendSkill
- wicked-garden-engineering-integrationSkill
- wicked-garden-engineering-large-scale-migrationSkill
- wicked-garden-engineering-migration-engineerSkill
- wicked-garden-engineering-patchSkill
- wicked-garden-engineeringSkill
- wicked-garden-engineering-solution-architectSkill
- wicked-garden-engineering-system-designSkill
- wicked-garden-engineering-unit-test-qualitySkill
- wicked-garden-governed-workerSkill
- wicked-garden-groundSkill
- wicked-garden-jam-brainstorm-facilitatorSkill
- wicked-garden-jam-councilSkill
- wicked-garden-jamSkill
- wicked-garden-learnSkill
- wicked-garden-mcp-scaffoldSkill
- wicked-garden-mcpSkill
- wicked-garden-mem-captureSkill
- wicked-garden-mem-ingestSkill
- wicked-garden-memSkill
- wicked-garden-personaSkill
- wicked-garden-platform-auditSkill
- wicked-garden-platform-compliance-officerSkill
- wicked-garden-platform-complianceSkill
- wicked-garden-platform-errorsSkill
- wicked-garden-platform-gate-benchmark-rebaselineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 79
No silent drop: a requirement dropped from a domain needs disposition:"drop"
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Domain Modeler
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. Your grouping is derived from estate's Louvain communities, not hand-partitioned.
Contract you emit against
Same vendored domain-model schema as the extractor (1.1.0; 1.0.0 documents
stay valid). 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, and core groups its domains by package
directory (the parent directory of each behaviour's file; it sets no cluster_id),
because dense modern code collapses into one community. 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 builds the authoritative domains itself 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 coverage evaluator). 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 saves the requirements graph into the estate store (domain, requirement and business-rule nodes,SatisfiedByedges to code — the source of truth crew reads);--outalso writes it as therequirements_graph.jsonexport this step validates (a capability plan, not a code skeleton). It fails closed below the configured minimum (writes nothing, non-zero exit, and says "N% real requirements, minimum M% (…)") — real requirements (behaviours with a business rule at or above the confidence threshold, or a validated requirement; placeholders never count) must reach at least that share of the behaviours in product code (the repository's own minimum, elseWICKED_REQUIREMENTS_MIN_COVERAGE_PCT, which crew exports from itsrequirementsGraph.minCoveragePct, else 80). 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. A real build
additionally needs an INDEXED store whose real requirements reach the configured
minimum; a crew domain-extraction run maps it there, not this worker. Full field map:
the wicked-garden-domain skill's refs/domain-model-emit.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

