Split MATTER.md skill into using + building-clients#48
Conversation
Replace managing-matter-md with two skills targeting distinct audiences: - using-matter-md: operational guidance for an agent doing matter work — when to read MATTER.md, what context is durable enough to write, how to edit without bloating it. - building-matter-md-clients: the convention/spec for harnesses adding MATTER.md support — discovery (MATTER.md at vault root), load lifecycle, client-owned conflict resolution. Keeps the convention loose: body is freeform Markdown, sections are illustrative not normative, edits go through plain file tools. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Judicial ReviewAdds two new MATTER.md skills and updates the README listing; changes are documentation-only and align with the described split. No security, data integrity, or compliance risks identified. No significant issues found. This code is cleared to ship. Legal-Grade review by Thurgood | Re-review with |
DB Cooper Database ReviewNo database-related changes detected in this PR; documentation-only additions and README update. No migration, query, or storage risks observed. No database risks found. Migrations and DB-impacting changes look safe. DB review by DB Cooper | Re-run with |
Oppenheimer Cleanup ReviewRepo-wide search found no remaining references to the removed managing-matter-md skill, and the new skill docs plus README references are internally consistent. No safe simplification opportunities identified in this diff. No cleanup opportunities found. This code is already lean. Cleanup review by Oppenheimer | Re-run with |
1 participant
What
Replaces the single
managing-matter-mdskill with two skills aimed at distinct audiences.MATTER.mdis the durable orientation file for a legal matter — the matter-level equivalent of a project instructions file. The original skill mixed agent behavior with implementer/spec guidance in one doc; this splits them.using-matter-md— operational guidance for an agent doing matter work: when to readMATTER.md, what context is durable enough to write, how to edit without bloating it (link to sources, don't copy; keep it bounded).building-matter-md-clients— the convention for a harness addingMATTER.mdsupport: discovery (MATTER.mdat the vault root), load lifecycle, client-owned conflict resolution.Design stance
Three layers, deliberately kept simple:
The convention stays loose on purpose — legal work varies too much to fix a schema. Body is freeform Markdown, sections are illustrative not normative, and edits go through plain file tools (no required tool surface, no locking model dictated).
Changes
skills/casedev/using-matter-md/SKILL.mdskills/casedev/building-matter-md-clients/SKILL.mdskills/casedev/managing-matter-md/SKILL.md🤖 Generated with Claude Code