From ritual
Use to create or update specification docs in docs/specs/ — checks alignment with parent domain knowledge and design decisions
npx claudepluginhub yanekyuk/arcana --plugin ritualThis skill is limited to using the following tools:
You are creating or updating a specification document.
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 specification document.
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 specs. If the field is missing or empty, proceed without directives.
docs/domain/ and docs/decisions/ for related tagsdocs/specs/<kebab-case-title>.md:---
title: "<descriptive title>"
type: spec
tags: [<lowercase, hyphen-separated, matching module/directory names>]
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
---
## Behavior
<What the feature/fix does>
## Constraints
<Rules derived from domain knowledge>
## Acceptance Criteria
<Testable conditions>
updated dateCommit the spec:
git add docs/specs/<filename>.md
git commit -m "docs: add/update spec — <title>"