$ cat ~/map/pi-config.md
pi-config
A ready-to-clone global Pi configuration with agents, skills, and prompt templates.
templates✓ Oct 16
Facts
- repository
- github.com/HazAT/pi-config ↗
- GitHub Stars
- ★ 454
- Forks
- 43
- license
- MIT
- npm / mo
- —
- last push
- Aug 25, 2026
install
mkdir -p ~/.pi && git clone git@github.com:HazAT/pi-config ~/.pi/agent && cd ~/.pi/agent && ./setup.sh## TL;DR
Personal global pi configuration repo by HazAT — clone to ~/.pi/agent/ and run setup.sh to get a /plan, /todos, /execute, /review session-file workflow plus skills, prompt templates, and extensions.
## Key points
- $Setup: clone the repo to ~/.pi/agent/ and run ./setup.sh — it requires that location, preserves an existing settings.json, installs the configured Git-backed packages, and installs the macOS Harness runtime with uv on macOS. Provider credentials go into ~/.pi/agent/auth.json, then restart pi.
- $The session-file workflow is four explicit prompt commands: /plan loads the planning skill and records the selected approach; /todos converts the plan into worker-ready todos; /execute runs Superconductor orchestration with sequential source-writing workers, one focused verified commit each; /review runs an independent local review team and repairs blocking findings, bounded to two rounds.
- $Handover state is plain Markdown beside the current session — ${PI_SESSION_FILE%.jsonl}.plan.md, .todos.md, and .review.md. There is no sidecar directory, repository run store, or custom JSONL state; the current coordinator owns all writes, and /review needs only the session JSONL.
- $Orchestration uses the sc CLI directly; before launching agents or teams, read skills/superconductor/SKILL.md and run sc instructions orchestration — live instructions override remembered syntax. Workers share the checkout, run sequentially, and never push; review team members are independent and read-only.
- $Repository layout: prompts/*.md (plan, todos, execute, review, superconductor-setup), skills/ directories (plan, write-todos, worker, review, scout, superconductor, setup-superconductor-project, pi-extension-development, commit), extensions/execute-command (an execute_command tool for self-invoked slash commands), and settings.json, models.json, mcp.json.
- $Updates: cd ~/.pi/agent, git pull, then ./setup.sh again.
## FAQ
Q Where does the workflow state live?
In plain Markdown next to the session JSONL, derived from PI_SESSION_FILE — the .plan.md, .todos.md, and .review.md files. There is no sidecar directory, run store, membership system, or custom state, and workers never edit the todos file themselves.
## References
## Related entries
Last updated: Aug 31, 2026