← ClaudeAtlas

garelier-corelisted

Garelier-only: fire in a `__garelier/<pm_id>/` project or on explicit Garelier/core invocation, not on generic protocol/state-machine wording. Shared protocol, state machine, retention policy, and templates that the role skills (garelier-pm, garelier-dock, garelier-worker, garelier-scout, garelier-smith) require. Consult when working as any Garelier role; handling files under `__garelier/` (control or runtime subtrees); creating worktrees or AGENTS.md for AI agents; reading/writing assignment.md, report.md, STATE.md, the runtime manifest, blueprints, inspections, delegated request intake, scheduled jobs, history archives, or high-volume daily reports.
aby-studio-works/garelier · ★ 0 · Data & Documents · score 75
Install: claude install-skill aby-studio-works/garelier
# Garelier Core This skill is the shared reference library for the Garelier multi-agent coordination framework. The role skills (garelier-pm, garelier-dock, garelier-worker, garelier-scout, garelier-smith) each declare a dependency on the definitions in this skill. This file is a **lean index**: the detail lives in the companion docs (`protocol.md`, `state_machine.md`, …) and in `references/` (DEC-034). Open the one you need; do not bulk-load everything. ## Root terms - `control_root`: the root that owns `__garelier/`. - `garelier_root`: `control_root/__garelier`. - `target_root`: the target project Git root. - Plant-Lithosphere: `control_root == target_root`. - Plant-Crust: `control_root != target_root`; the active container owns `__garelier/`, and `target_root` is normally `container_root/target`. `workfolder_root` is only the `crust.toml` registry and does not own `workfolder_root/__garelier`. Garelier control/runtime paths are relative to `control_root`. Target project files, Git operations, worktrees, and quality gates are relative to `target_root` or a checkout created from it. In Plant-Crust, `target_root/__garelier` is forbidden. Plant-Crust cross-container rule: PM may read registered containers and write per-container Dock requests; Dock and all subordinate roles are active-container scoped and must not read or write sibling containers. ## When you are reading this You are operating in a Garelier project. A role-specific skill is your primary instructio