kyles-domain-modeling

Audit and exercise evidence-grounded domain models using a 13-dimension rubric and Domain Contract template.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/thorsenk/skills --skill kyles-domain-modeling-thorsenk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kyles-domain-modeling
Source: https://github.com/thorsenk/skills/tree/main/retired/kyles-domain-modeling
Command: npx skills add https://github.com/thorsenk/skills --skill kyles-domain-modeling-thorsenk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Domain knowledge often gets scattered across UI code, storage schemas, routes, and tests without an explicit model, causing inconsistent vocabulary, hidden business rules, and fragile implementations. This retired package (preserved for historical reference) provides a structured way to audit existing documentation or run a guided modeling exercise before implementation spreads domain logic. ## Core Features & Use Cases - Audit Mode: Scores project documentation against 13 fixed rubric dimensions (shared language, lifecycle modeling, invariants, boundaries, evidence quality) with a 0-5 scale, severity-tagged findings, and an overall readiness grade. - Exercise Mode: Facilitates a gated discovery interview that produces a Domain Contract covering shared language, concepts, state axes, relationships, rules, workflows, and an evidence register. - Documentation Inventory Script: Runs scripts/collect_domain_docs.py to scan project docs, count domain keywords, and surface heuristic terminology candidates from headings, tables, and JSON schemas. - Use Case: Before building a multi-state workflow feature, run the audit to verify that lifecycles, invariants, and ownership rules are documented well enough to implement safely. ## Quick Start Ask the agent to audit my project's documentation for domain modeling readiness using the 13-dimension rubric and report the highest-priority gaps.

Frequently Asked Questions about kyles-domain-modeling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a project's domain model documentation?▼

Run audit mode, which inspects product docs, specs, ADRs, and schemas before code, then scores 13 fixed rubric dimensions from 0 to 5. The output includes a verdict, scorecard, severity-tagged findings, and recommended next steps, all traceable to evidence.

What is a Domain Contract in domain-driven design exercises?▼

A Domain Contract is a structured artifact capturing shared language, core concepts, bounded contexts, lifecycle state axes, relationships, rules and invariants, workflows, and an evidence register. It is complete when terms are defined, state axes are separated, and high-risk invariants are testable.

When should I use audit mode versus exercise mode?▼

Use audit mode when documentation exists and can be inspected for scoring. Use exercise mode when documentation is missing, aspirational, or the project is greenfield, or when the user asks to create a domain model, glossary, or shared language from scratch.

Can I use this retired skill for new domain modeling work?▼

No. The package is retired and preserved only for historical reference; its frontmatter and instructions explicitly say not to install or use it for new work. Use the active upstream domain-modeling skill instead.

What does the collect_domain_docs.py script do?▼

It walks a project tree, inventories documentation files, counts domain-related keywords, and extracts heuristic terminology candidates from headings, tables, and JSON schemas. Results are emitted as Markdown or JSON, and terms are treated as unverified leads until project evidence confirms them.