Author or update amendment records in openEHR specification documents — the master00-amendmentrecord.adoc table in specifications-XX repos. This skill should be used when the user asks to add or update an amendment entry, add a CR/PR reference, mark a release boundary, or update the latestissue/latestissuedate…
Create or edit openEHR specification documents — the AsciiDoc sources, manifest.json, and boilerplate includes in specifications-XX repos. This skill should be used when the user asks to create a new spec, add or edit a chapter/section, set up master.adoc, edit a spec manifest.json, or work on .adoc files in a…
Generate openEHR class documentation — class-definition tables, effective views, and UML class/package diagrams — from BMM schemas with the bmm-publisher tool, for specifications-XX repos and their docs/UML/ content. This skill should be used when the user asks to regenerate class tables, run bmm-publisher, generate…
Patterns for writing production-quality openEHR specification prose — overviews, class/concept semantics, design rationale, and clinical examples — in specifications-XX repos. This skill should be used when the user asks how to phrase or improve spec prose, draft a package/class description, write a design-rationale…
Manage the openEHR specification governance lifecycle — releases, change requests (CR/PR), and lifecycle states (DEVELOPMENT/TRIAL/STABLE…). This skill should be used when the user asks to create or tag a release, prepare a release branch, update the manifest for a release, submit or manage a CR/PR, promote a spec's…
Create, edit, or review the openEHR ITS-REST API sources (OpenAPI 3.0 YAML + Markdown) in the specifications-ITS-REST repo. This skill should be used when the user asks to add or edit a REST endpoint/operation/schema/response, write an operation description, review the ITS-REST spec, or update its amendment record.…
Review an openEHR specification document for quality, completeness, and convention compliance in specifications-XX repos. This skill should be used when the user asks to review, lint, or quality-check an openEHR spec, validate its conventions, or run a pre-release review. Not for archetype/template review…