Imported from marcosdh1987/company-brain-template (.opencode/skills/update_domain_context/SKILL.md). Install upstream with npx skills add marcosdh1987/company-brain-template --skill update_domain_context. Copyright stays with the author.

Skill: update_domain_context

Name: update_domain_context
Author: marcosdh1987

Purpose

Absorb one business change consistently (context, glossary, requirements, architecture) instead of patching one file and letting the rest drift.

Required Input

The change, in one or two sentences, and its source (decision, meeting, incident, named person).

Execution Rules

Classify: entity | business rule | integration | vocabulary | scope | ownership. One change may touch several.
Grep the brain for every mention of the affected concepts; list files to touch before editing any.
Update each file respecting its schema and IDs. New rules take the next BR number; renamed terms keep a synonym row pointing to the canonical entry; replaced facts are marked SUPERSEDED, never deleted.
If the change contradicts a recorded decision, do not silently edit — flag that a superseding DEC is needed (record_decision).
make validate. Summarize what changed, citing the source.

Output Format

Files touched with one-line diffs and provenance; any DEC flagged for supersession.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

{ "ocm": "1", "id": "marcosdh1987-company-brain-template-update-domain-context", "kind": "skill", "name": "update_domain_context", "description": "Use when the business changed — entity, rule, integration, vocabulary or scope — and the brain must absorb it without drifting - locates every affected section, updates them consistently with status and source.", "publisher": "marcosdh1987", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use when the business changed — entity, rule, integration, vocabulary or scope — and the brain must absorb it without drifting - locates every affected section, updates them consistently with status and source." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/marcosdh1987/company-brain-template", "path": ".opencode/skills/update_domain_context/SKILL.md", "ref": "1ba1b649e5204ea207dbe00598a53feefc2fd599", "url": "https://github.com/marcosdh1987/company-brain-template/blob/1ba1b649e5204ea207dbe00598a53feefc2fd599/.opencode/skills/update_domain_context/SKILL.md", "key": "marcosdh1987/company-brain-template/.opencode/skills/update_domain_context/SKILL.md" } }, "instructions": "# Skill: update_domain_context\n\n## Purpose\n\nAbsorb one business change consistently (context, glossary, requirements,\narchitecture) instead of patching one file and letting the rest drift.\n\n## Required Input\n\n- The change, in one or two sentences, and its source (decision, meeting,\n incident, named person).\n\n## Execution Rules\n\n1. Classify: entity | business rule | integration | vocabulary | scope |\n ownership. One change may touch several.\n2. Grep the brain for every mention of the affected concepts; list files to\n touch before editing any.\n3. Update each file respecting its schema and I", "cost": { "context_tokens": 267 } }

update_domain_context

About

Skill: update_domain_context

Purpose

Required Input

Execution Rules

Output Format

Use it

Manifest

Reviews