Context: switching persistent coding agents off pi to our own Omni/Agent binary (epic t-759). Pi's system prompt is well-tuned for coding work — Ben wants to steal it (with attribution / adaptation) for our dedicated coding agents rather than writing from scratch.
What to do:
- Locate pi's system prompt in the pi-agent-core source (likely in @mariozechner/pi-coding-agent — check node_modules or the published package).
- Read it carefully, understand the structure (role framing, tool usage guidance, code style rules, safety rails, etc.).
- Port it into Omni/Agent as the default system prompt for the coding agent variant, adapted for our:
- tool set (bild, task CLI, our code layout conventions)
- repo conventions (the Omni style guide, bild targets, Haskell/Python/Nix mix)
- Task-Id commit trailer workflow
- Review lifecycle (Todo → InProgress → Review → Done)
- Keep a CHANGES note in the file showing what was adapted and why.
Acceptance criteria:
- New system prompt file checked in under Omni/Agent/ (or wherever prompts live).
- Wired into the agent binary so persistent coding agents get it by default.
- Short doc/comment at the top crediting pi as the source of the original structure.
Dependencies: t-759 epic. Can land independently of the compaction design task.
We should also consolidate the various coding skills and prompts scattered around the repo (e.g. dev-system.md, coder.md, overseer.md, pi system prompts, skill files) into a canonical version. One source of truth for what a coding agent's system prompt and skills should be, rather than multiple divergent copies.