grimoire-loop
Installation
SKILL.md
Coordinate the selected work; specialists own their methods. Run this workflow only on explicit user invocation, not automatically from a specialist or a general implementation request.
1. Choose the execution path
Choose the smallest useful path; these are defaults, not mandatory stage bundles.
- Direct: for clear, bounded, reversible work with no recovery, handoff, or reusable planning need, default to implement → targeted verification → report. Do not invoke plan or create a Plan file, plan directory, or viewer merely because loop was selected. Explicitly requested planning or artifacts still apply.
- Structured: when sequencing or consequential approach decisions make a plan useful, default to plan → implement → test → review + check → assess → affected fixes/checks → final integrated verification → format → report. Risk determines check depth, not a compulsory document.
- Orchestrated: when human checkpoints, delegated/parallel handoffs, or recovery across sessions need coordination, adapt Direct or Structured to that need. Coordination alone does not require a plan, subagents, or all references; load only the relevant branch below.
2. Establish the execution contract
Use the request to determine scope, enabled stages/order, write permissions, human gates, and required evidence. Record special ownership or fix/repetition limits only when relevant. Natural language and conversation context suffice; no contract artifact is required. Later instructions revise remaining work.
- Every stage/substage is independently selectable, reorderable, or human-owned—including planning/persistence, test design/authoring/execution, assessment, fixes, repetition, final verification, formatting, and reporting. Users may add stages/checkpoints.
- Apply defaults only to unspecified choices. “Only review” excludes other work stages. Disabling a parent stage disables its substages unless explicitly retained; exclusions never grant other write permissions.
- Do not restore a disabled stage through a specialist's defaults, risk recommendation, automatic fix, or renamed check. This applies inline and to delegates. Omitted work is not passed; surface conflicting evidence requirements rather than bypass exclusions.
- All work stays within scope and authority. Fixes require both fix and corresponding write permission; honor single-pass/user limits. Risk does not authorize delegation or excluded work. Higher-priority safety and authority constraints still apply.
- Honor required human gates: stop before gated work, set waiting for user, and end the turn. Automated success is not human approval; checkpoints never expand permissions. Add discretionary checkpoints only when authorized. Missing authority, material ambiguity, required human evidence, or unresolved unsafe/irreversible decisions still require a pause.