From ritual
Use to create or update domain knowledge docs (business rules, invariants, constraints) in docs/domain/ — triggers clash-check on decisions and specs
npx claudepluginhub yanekyuk/arcana --plugin ritualThis skill is limited to using the following tools:
You are creating or updating a domain knowledge document — business rules, invariants, and constraints that govern the system.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
You are creating or updating a domain knowledge document — business rules, invariants, and constraints that govern the system.
Directives: If docs/ritual-config.json exists, read directives.documentation from the config. These are soft guidelines that influence your documentation style, detail level, and terminology. Apply them when writing domain docs. If the field is missing or empty, proceed without directives.
docs/domain/<kebab-case-title>.md:---
title: "<descriptive title>"
type: domain
tags: [<lowercase, hyphen-separated, matching module/directory names>]
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
---
<Document the business rules, invariants, or constraints clearly and concisely.
Each rule should be a separate paragraph or bullet point.
Include rationale where known.>
git add docs/domain/<filename>.md
git commit -m "docs: add domain knowledge — <title>"
updated dategit add docs/domain/<filename>.md
git commit -m "docs: update domain knowledge — <title>"
Domain knowledge is the highest tier. Changes here can invalidate design decisions and specs.
Dispatch run-clash-check as a subagent (via the Agent tool) targeting both docs/decisions/ and docs/specs/. This is a depth-1 cascade — run-clash-check must NOT trigger further cascades.
Report: