agentleFS
mikeparcewskimikeparcewski/wicked-garden/skills/domain-modeler/SKILL.md

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.

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
  1. Very specific:

    No silent drop: a requirement dropped from a domain needs disposition:"drop"

    line 79

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read clusters from estate — the full-membership feed clusters --json --summary → [{id, size, members:[symbol_id], …}], via estate_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 advisory cluster_id).
  2. 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.
  3. Invoke core's domain-graph build. core_client().domain_graph(db, out) shells wicked-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, SatisfiedBy edges to code — the source of truth crew reads); --out also writes it as the requirements_graph.json export 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, else WICKED_REQUIREMENTS_MIN_COVERAGE_PCT, which crew exports from its requirementsGraph.minCoveragePct, else 80). There is no doc handed in and no --overlay: the store is the input. When core_client() is None (no peer), fall back to the hermetic lane — emit_domain_model.py assembles the doc and _mocks.BrainClient stands in.
  4. Validate core's output. Cross-check the built requirements_graph.json with scripts/domain/validate_domain_model.py (schema + hard invariants) before returning.

Invariants you must not break

  • domains is required; every domain has requirements and entities.
  • cluster_id is 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 a disposition_reason, or it counts against coverage.
  • metadata.migration_mode ∈ {structural, functional} — functional (capability-grouped) is the default; structural is 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.