eforge-playbooklisted

> **Note:** In Pi, the native `/eforge:playbook` command provides interactive TUI selectors and panels for Run, List, Promote, and Demote. For Create and Edit (which require conversational reasoning), the native command delegates to this skill. The skill also serves as fallback in non-interactive contexts. # /eforge:playbook Manage eforge playbooks — reusable templates for recurring workflows that eforge can invoke on demand. Playbooks live in one of three storage tiers: - `~/.config/eforge/playbooks/` — **user** scope (cross-project, personal) - `eforge/playbooks/` — **project-team** scope (committed, shared with the team) - `.eforge/playbooks/` — **project-local** scope (gitignored, personal draft) A lower-tier playbook with the same name **shadows** a higher-tier one. eforge always resolves the most-specific tier. ## Playbook Modes Every playbook has a `mode` field in its frontmatter: - **`mode: autonomous`** — eforge builds the playbook end-to-end without further prompting. Hand-off-and-forget: the daemon enqueues it and runs it. Suitable for mechanical, repeatable workflows where the build agent does not need to consult the user mid-run. - **`mode: planning`** — running the playbook triggers an investigation-first workflow. The agent loads the playbook, performs the investigation guided by the playbook's Goal, Acceptance criteria, and Notes for the planner, creates a session plan with concrete findings and action items, and continues the planning conversation inte