pi-engram-extensions

Document architectural decisions as engraph ADRs. Store context, options considered, rationale, and consequences for queryable decision history.

Every commit must reference a valid engram task UUID. Covers format, validation, and why --no-verify is prohibited.

Orchestrator agent loop. Coordinates work across subagents using engram as shared state. Search before acting, dispatch by UUID, validate before finishing.

Plan feature implementation by creating an engram task hierarchy. Not a markdown plan — a queryable task tree any agent can retrieve.

Universal session end protocol. Run at the end of every agent session — closes open tasks, generates a handoff summary, syncs to remote, and validates state.

Universal session start protocol. Run at the beginning of every agent session — syncs from remote, opens a session, loads prior context, and surfaces the next action.

Subagent registration protocol. Use when assigned a task UUID by an orchestrator — claim the task, pull context from engram, store all findings, and report results back.

Systematic debugging with engram evidence trails. Store investigation as reasoning chains — queryable and reviewable by future agents.

Test-driven development with engram validation checkpoints. Write test first, watch it fail, write minimal code, store evidence at each phase.

Use engram as persistent memory for all work. Covers the per-turn write rule — every bash, edit, or write call must be followed by engram_context_create or engram_reasoning_create in the same turn. Load this skill whenever the engram-write-first warning appears or when starting any task that produces findings.

Use engram workflows (state machines) to track structured processes — feature development, bug fixes, incidents, releases, ADRs, research spikes, and custom flows.

Configure or reconfigure .pi/failover.json and .pi/model-routing.json for the model-failover extension. Checks which AI providers are currently configured in pi (OAuth tokens and API key env vars), cross-references the existing failover list, asks the user to confirm which subscriptions are still active, then updates the configs to reflect available models with correct priority ordering. Use this when setting up a new machine, after a subscription change, or to audit the current failover configuration.

Full workspace bootstrap for the pi-engram-extensions package. Checks prerequisites (pi, node, engram CLI), verifies the package is installed and extensions are loading, then runs the model-failover setup to configure failover.json and model-routing.json. Use this when installing on a new machine, after a subscription change, or when handing off to a new agent or developer.

Install the engram CLI binary and bootstrap a project workspace. Covers all platforms (Linux, macOS, Windows, NixOS) via the one-line installer, direct binary download, nix, or cargo. Also runs the post-install bootstrap sequence (workspace init, agent registration, skills install, commit hook). Use when engram is missing, needs upgrading, or a new project needs initialising.