Menu
Implement a piece of work based on a spec or set of tickets.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Write messages, comments, PR reviews, Slack posts, and other prose in Sean's voice. Use when drafting anything that will be sent under Sean's name — code review comments, postmortem feedback, Slack messages, GitHub comments, coaching notes, design feedback, strategic takes. Triggers: 'write like me', 'in my voice', 'draft a comment for me', 'sound like me', 'sharpen this', 'this still sounds like AI'.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets, and resolve them one at a time until the way to the destination is clear.
Move todos through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs. Maps to pi's built-in todo tool; see ../todo-tracker.md for the full tracker → tool mapping.
Turn the current conversation into a spec and publish it as a todo — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet todos, each declaring its blocking edges — create-then-wire so every blocker id is real.
| name | implement |
| description | Implement a piece of work based on a spec or set of tickets. |
| disable-model-invocation | true |
Work the todo frontier defined in ../todo-tracker.md. Pick the next unblocked ready-for-agent todo, work it to completion, then repeat — one ticket at a time, clearing context between.
Follow the frontier algorithm in ../todo-tracker.md:
todo({ action: "list" }) — list open todos.Blocked by: line in the body; verify all listed blockers have status: "done".assigned_to_session set).todo({ action: "claim", id: "TODO-xxxx" }).The todo body is the spec. Read it in full before writing any code.
Use /tdd at pre-agreed seams (interfaces, service boundaries, pure functions). During implementation:
Once all acceptance criteria are satisfied, run the full test suite once.
Run /code-review on the finished work.
Read and follow the commit skill at ~/.pi/agent/skills/commit — it is mandatory for every commit. Use Conventional Commits format with a polished, descriptive message.
todo({ action: "update", id: "TODO-xxxx", status: "done" })
Return to step 1. If there are no more unblocked todos on the frontier, stop and report.