shepherdlisted

# /shepherd — Conductor Quick Reference This file is a **quick-reference index**. Operational detail lives in the sibling files and agent profile files (see §XI). When this file points at one, load it. **Sprint-runner behavior is canonical in `agents/conductor.md`.** This file provides orientation and cross-references; for the binding dispatch procedure, pipeline steps, and halt codes, see `agents/conductor.md §Mandatory protocol`. --- ## 0. Read shepherd.toml first Every `/shepherd:*` invocation MUST start by reading `.claude/shepherd.toml` (or its `.local.toml` override). This file binds the framework to the project: branch patterns, gate commands, artifact paths, skill integration, MCP/CLI availability, ledger discipline. If missing, surface a warning and use the defaults documented in `${CLAUDE_PLUGIN_ROOT}/docs/configuration.md`. If broken (validation errors per `docs/configuration.md` §Validation), STOP and surface the error to the operator. Throughout this skill, references to: - `{patch_branch}` mean the resolved value of `branching.patch_branch_pattern` - `{sprint_branch}` mean `branching.sprint_branch_pattern` - `{paths.plans}`, `{paths.reports}`, `{paths.docs}`, `{paths.ctx}` mean the resolved `[paths]` values - `{gates.check}`, `{gates.lint}`, `{gates.format}` mean the resolved `[gates]` commands --- ## 0-bis. Token + cache discipline (foundational, always-on) Three doctrines form the always-on framework for keeping flock dispatches cheap, coherent, and