model
/model
Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close before design. Runs upstream of feature $kk:design as the first producer of the architecture flow, and emits artifacts $kk:review-architecture verifies. Triggers: "model the domain", "build a glossary", "domain reference", "bounded context", "what are the concepts here". NOT for behavi
- Author
- serpro69 ↗
- Repository
- claude-toolbox ↗
- Licence
- Apache-2.0
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 46
- Scripts
- 18
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 18 scripts in this package. Review them before installing, as Claude may execute them.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Scripts: evals/brownfield-update/test-files/gym/grading.go, evals/brownfield-update/test-files/gym/route.go, evals/brownfield-update/test-files/gym/wall.go, evals/hidden-invariant/test-files/campground/booking.go, evals/hidden-invariant/test-files/campground/gate.go, evals/hidden-invariant/test-files/campground/occupancy.go, evals/hidden-invariant/test-files/campground/site.go, evals/kit-format/test-files/
What it does and when to use it
Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close before design. Runs upstream of feature $kk:design as the first producer of the architecture flow, and emits artifacts $kk:review-architecture verifies. Triggers: "model the domain", "build a glossary", "domain reference", "bounded context", "what are the concepts here". NOT for behavi
Triggers from the description
Original author description
Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close before design. Runs upstream of feature $kk:design as the first producer of the architecture flow, and emits artifacts $kk:review-architecture verifies. Triggers: "model the domain", "build a glossary", "domain reference", "bounded context", "what are the concepts here". NOT for behavi
How it works
- Conventions
- Workflow
- Required Outputs
SKILL.md preview
--- name: model description: | Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close before design. Runs upstream of feature $kk:design as the first producer of the architecture flow, and emits artifacts $kk:review-architecture verifies. Triggers: "model the domain", "build a glossary", "domain reference", "bounded context", "what are the concepts here". NOT for behavioral code review or writing a feature design doc. --- <!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh --> # Domain Modelling — the steady-state kit **Goal: produce a provenance-clean domain-reference kit and, above all, a decision queue of precise, role-tagged questions a human can close.** The queue is the primary output — artifact count and model sophistication are explicitly not the metric. `$kk:model` is the first **producer** of the architecture flow: it runs at information-architecture altitude (what the domain's concepts are, where they bind to code, and which questions about them only a human can close), upstream of feature `$kk:design` and never called by it. It writes files and interacts with you mid-flow — it is a main-session skill, not a read-only reviewer. ## Conventions - **Capy knowledge base** — read [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md); searched at intake (`kk:arch-decisions`, `kk:project-conventions`), indexed at close. - **Shared producer guards** — four workflow guards, each citing the field failure it prevents. Load all four before acting: - [shared-requirements-harvesting.md](shared-requirements-harvesting.md) — quote the real asks before modelling (F1). - [shared-open-question-pass.md](shared-open-question-pass.md) — verification asks new questions, not just re-confirms (F4). - [shared-fact-flip-propagation.md](shared-fact-flip-propagation.md) — a contradicted fact is fixed everywhere in-session (F2). - [shared-contact-ratio-guard.md](shared-contact-ratio-guard.md) — at N:0 artifacts-to-contacts, the next step is a conversation (F5). - **Profiles are not consulted** — `$kk:model` is language-agnostic in M2; archaeology reads code directly. Profile enrichment is deferred (design §8). ## Workflow **Mandatory order — instructions before subject matter.** The flow is strictly sequential. Do **not** read code to model it, draft any kit page, or engage the domain beyond a mode-detecting directory/keyword scan until every instruction file is loaded: this SKILL.md, the process file [model-process.md](model-process.md), the reading method [archaeology.md](archaeology.md), the output contract [kit-contract.md](kit-contract.md), all four shared guards above, and the shared capy protocol. This ordering is load-bearing: with domain code in context before the contracts load, the model emits plausible terms and skips the methodology that makes them trustworthy. 1. **Load instructions.** Read [model-process.md](model-process.md) (the detailed seven-phase workflow), [archaeology.md](archaeology.md), [kit-contract.md](kit-contract.md), all four shared guards — [shared-requirements-harvesting.md](shared-requirements-harvesting.md), [shared-open-question-pass.md](shared-open-question-pass.md), [shared-fact-flip-propagation.md](shared-fact-flip-propagation.md), [shared-contact-ratio-guard.md](shared-contact-ratio-guard.md) — and [shared-capy-knowledge-protocol.md](shared-capy-knowledge-protocol.md). Minimal early scope — a directory listing or a keyword scan of the request — is permitted only to drive mode detection. 2. **Execute the seven phases** per [model-process.md](model-process.md): 1. **Scope intake** — establish the bounded context, the **forcing question** (the feature/ticket that bounds what is worth modelling), and the **mode** (greenfield: no kit exists → produce the two pages; brownfield: an existing kit is read in full first and all changes are deltas, status markers never flipped unilaterally). Run the capy knowledge search. 2. **Requirements-harvesting gate** *(guard, F1)* — read every linked ticket + one hop; quote the actual asks into working notes before any modelling. 3. **Archaeology** — read code **state → time → invariants** per [archaeology.md](archaeology.md); two-clock discipline (code-clock facts verifiable, intent stays `proposed`). 4. **Draft the kit** per [kit-contract.md](kit-contract.md) — glossary page + divergences/traps page (+ conventions index if the home has none). 5. **Verify** — at least one confirm-pass **plus at least one open-question pass** *(guard, F4)*. 6. **Self-check** — conventions-bind-author lint: the produced pages obey the kit's own declared conventions. 7. **Surface & close** — present the **decision queue** (each RQ precise, decidable, role-tagged); apply the **contact-ratio guard** *(F5)*; in brownfield, **fact-flip propagation** *(F2)* on any contradicted recorded fact; index non-obvious rationale to `kk:arch-decisions`. ## Required Outputs - [ ] The two durable kit pages (glossary + traps) for the context, provenance-clean, per [kit-contract.md](kit-contract.md) (+ conventions index if the home lacked one). - [ ] The **decision queue** — precise, decidable, role-tagged questions — presented inline and appended to the active feature's `docs/feat/wip/<feature>/design.md` under an **Open Questions** heading when that directory exists. - [ ] Contact-ratio guard applied; brownfield fact-flips propagated across the workspace. - [ ] Non-obvious modelling rationale indexed to `kk:arch-decisions`.
Files in this package (46)
- SKILL.md 6 KB
- archaeology.md 3 KB
- kit-contract.md 12 KB
- model-process.md 9 KB
- shared-capy-knowledge-protocol.md 2 KB
- shared-contact-ratio-guard.md 2 KB
- shared-fact-flip-propagation.md 2 KB
- shared-open-question-pass.md 3 KB
- shared-requirements-harvesting.md 2 KB
- evals/brownfield-update/eval.json 4 KB
- evals/brownfield-update/oracle/gold-deltas.json 4 KB
- evals/brownfield-update/test-files/docs/architecture/index.md 1 KB
- evals/brownfield-update/test-files/docs/architecture/routesetting-traps.md 1 KB
- evals/brownfield-update/test-files/docs/architecture/routesetting.md 3 KB
- evals/brownfield-update/test-files/gym/go.mod 1 KB
- evals/brownfield-update/test-files/gym/grading.go 1 KB
- evals/brownfield-update/test-files/gym/route.go 1 KB
- evals/brownfield-update/test-files/gym/wall.go 1 KB
- evals/hidden-invariant/eval.json 4 KB
- evals/hidden-invariant/oracle/gold-invariant.json 3 KB
- evals/hidden-invariant/test-files/campground/booking.go 1 KB
- evals/hidden-invariant/test-files/campground/gate.go 1 KB
- evals/hidden-invariant/test-files/campground/go.mod 1 KB
- evals/hidden-invariant/test-files/campground/occupancy.go 1 KB
- evals/hidden-invariant/test-files/campground/site.go 1 KB
- evals/kit-format/eval.json 6 KB
- evals/kit-format/oracle/kit-conventions-checklist.json 5 KB
- evals/kit-format/test-files/bikeshare/bike.go 1 KB
- evals/kit-format/test-files/bikeshare/dock.go 1 KB
- evals/kit-format/test-files/bikeshare/go.mod 1 KB
- evals/kit-format/test-files/bikeshare/policy.go 1 KB
- evals/kit-format/test-files/bikeshare/ride.go 1 KB
- evals/requirements-gate/eval.json 4 KB
- evals/requirements-gate/oracle/gold-harvest.json 3 KB
- evals/requirements-gate/test-files/ferry/boarding.go 1 KB
- evals/requirements-gate/test-files/ferry/go.mod 1 KB
- evals/requirements-gate/test-files/ferry/reservation.go 1 KB
- evals/requirements-gate/test-files/ferry/sailing.go 1 KB
- evals/requirements-gate/test-files/ferry/tickets/FERRY-12.md 1 KB
- evals/requirements-gate/test-files/ferry/tickets/FERRY-31.md 1 KB
- evals/scope-pushback/eval.json 3 KB
- evals/scope-pushback/test-files/apiary/colony.go 1 KB
- evals/scope-pushback/test-files/apiary/go.mod 1 KB
- evals/scope-pushback/test-files/apiary/harvest.go 1 KB
- evals/scope-pushback/test-files/apiary/hive.go 1 KB
- evals/scope-pushback/test-files/apiary/inspection.go 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · serpro69/claude-toolbox | 90 | Apache-2.0 |
| vecten/vecten-open | 100 | Apache-2.0 |
| ilanbm/kpopper | 91 | MIT |
| serpro69/claude-toolbox | 90 | Apache-2.0 |
| hdkhosravian/dynamic-harness | 90 | MIT |
| Alejo2075/claude-code-aws | 90 | MIT |
| florianbuetow/claude-code | 90 | MIT |
| laaielichter/Godotwright | 86 | MIT |
| laaielichter/Threesmith | 86 | MIT |
Database snapshot: 13.11.2026 · package version 84f8312e38f1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100domain-model
Create or review a domain model — bounded contexts, entities, value objects, aggregates, domain events, relationships. Use when: domain model, bounded context, ubiquitous language, context map, domain design, domain analysis, domain events, aggregate, entities, DDD analysis. - 100s-domain-modeling
Build and sharpen a project's domain model. Use when domain terminology, relationships or rules change, when writing or editing a GLOSSARY.md, or when recording or editing an ADR. - 100domain-modeling
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR. - 100domain-modeling
Build and sharpen a project's domain model. Use when discussing project terminology, writing or editing GLOSSARY.md, or recording or editing an ADR. - 100domain-modeling
Use when building or sharpening a project's domain model, discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR. - 100domain-modeling
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.