leduykhuong-daniel

Use when applying Documentation-as-Code across many teams or a super-app / multi-repo / monorepo with several mini-apps — how to lay out per-team docs, own API contracts at boundaries, keep one traceability matrix across teams, and run the gate per changed area. The advanced (Lesson 6) counterpart to single-project docs-as-code.

Use when wiring the docs quality gate into CI/CD — turning docs-as-code:validate into a check that blocks pull requests on a docs/frontmatter/link failure. Covers GitHub Actions, GitLab CI, and a generic shell gate, plus making CODEOWNERS enforce doc review.

Use when acting on an existing or in-progress Documentation-as-Code repo — assessing and scaffolding it, authoring or promoting a BRD/PRD/FR/NFR/ADR/Epic/Story/Test artifact, building a traceability matrix, versioning an inter-team API contract, validating frontmatter/links, auditing gaps and drift, or preparing a docs pull request. Routes the request to the right docs-as-code:* command. For a first-time conceptual introduction, defer to the docs-as-code-intro skill.

Use when measuring or reporting documentation health — explains the four docs-health metrics (coverage, freshness, contribution, contract-sync) that docs-as-code:audit reports, how each is computed, what target to hold, and how to read a declining one. For setting a docs SLO or a weekly health review.

Use when introducing a team to Documentation-as-Code — explains the principle, the minimum toolchain (Markdown + Git + PR review + CI), and the first three steps to adopt it on an existing project.

Use when explaining how an operational ontology becomes a digital twin — covers the twinning loop (model + live data + behavior), the 5-level maturity ladder, and how AI agents operate on a twin. Pairs with ontology-as-code-intro.

Use when wiring Ontology-as-Code into Git and CI — branching for an ontology, reviewing a schema change as a pull request, the four CI gates (validate PASS / expect-FAIL / codegen smoke / drift), semver for schema evolution, and the codegen pipeline. Trigger whenever the user wants CI, a pipeline, a gate, versioning, breaking-change rules, or to generate an SDK/diagram for their ontology/digital twin.

Use when introducing a team to Ontology-as-Code — explains the operational ontology concept, the 6-atom model (object/attribute/link/action/policy/event), how it differs from BI semantic layers, and the first steps to model one entity on LinkML.

Use when modeling any of the 6 atoms of an ontology/digital twin — ObjectType, AttributeType, LinkType, ActionType, PolicyType, EventType — the semantic-first way. Covers the business questions to ask before listing attributes, links as native slots, kinetic atoms as contracts, and data binding for twinning. Make sure to use this whenever the user wants to add, define, model, or create a domain object, attribute, relation/link, action, policy/rule, or event — even if they don't say 'ontology'.

Use for day-2 operations on a digital twin — adding, modifying, or deprecating a domain with breaking-change discipline, monitoring twin health (binding/freshness, governance ownership, event-stream, drift), and adopting ontology into an existing codebase. Trigger whenever the user wants to evolve, change, deprecate, or remove a domain concept, asks if a change is breaking, wants to health-check/audit a twin, or wants to bring ontology into a brownfield project.