Apo Seat — Development skill for Claude Code

APO Seat Kit — 10-minute setup

*From Tim Reilly, CloneTech Inc. The APO ("Agentic Product/Program Officer") is the Claude Code role that plans your work, spins up and coordinates builder agents, quality-gates everything, and hands you one board with exactly what needs your eyes — so you review finished work instead of supervising work-in-progress.*

Prerequisite

Set up "legible commits" first — it is included here as LEGIBLE-COMMITS.md (5 minutes, one CLAUDE.md paste) and also lives in its own repo, https://github.com/tldr-git/legible-commits, if you want to pull its updates separately. The APO assumes commits explain WHY and serve as institutional memory.

**How an agent knows whether it's already installed:** the paste leaves a heading in the repo's `CLAUDE.md`, exactly `## Commits & comments are institutional memory`. If that heading is present, skip this step; if absent, paste LEGIBLE-COMMITS.md's block into `CLAUDE.md` first. No guessing from git history.

Setup (once per project)

1. Clone the kit (keep the clone; your APO uses it to self-update):

   git clone https://github.com/tldr-git/apo-seat.git ~/apo-seat

   Updates later are just git -C ~/apo-seat pull — and your APO checks for them itself on boot (see APO.md §6).

0b. **A private GitHub remote, from day one.** The decision log is only useful if it outlives the laptop and other people's agents can read it. In the repo: `gh repo create --private --source . --push` (Private is the standard; public only if you mean to publish). From here on, committed means pushed; see LEGIBLE-COMMITS.md.

1. **Copy the seat into your repo:**

   your-repo/
     apo/
       APO.md           ← from this kit
       apo-memory.md    ← create empty, one line: "# APO seat memory"

2. **Paste this block into your project's `CLAUDE.md`** (create the file at the repo root if you don't have one):

   ## The APO seat
   When addressed as "APO" (or whe