Status
Answer the question "where is it?" honestly, from evidence, in under
twenty lines. Change nothing — not the board, not a title line, not a
stale claim you happen to notice. Say it is stale and let the loop recover it.
Read, then report
BOARD.md for the live picture · the last entries of RECORD.md · task title
lines for real states · git log for what actually landed.
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check_trace.py" .
Report, in this order
- Phase and width — onboard, plan, build, harden or deliver.
- In flight — each task, since when, on what model, and what its
supervisor last reported. A claim with no live agent is stale: say so.
Then one line per open sandbox, read from
devteam/.run/locks/*.sandbox
— task, step, id, whether the pid is live, and the root. A headless worker
is invisible to ListAgents (P-14b), so without this line a task that is
actively being worked reads here as a task with nobody on it.
- Waiting on the client — every open question, its class, and how long it
has been waiting. Put this above "done" if anything is here; it is the only
part the client can act on.
- Decided without the client — count, and the ones still cheap to
reverse (P-27).
- Progress, by evidence — requirements
discharged with acceptance
evidence recorded, out of the total. Not tasks closed; not a percentage
of anything. A task closed without its acceptance criterion run has not
discharged its requirement (P-5).
- Blocked — what, and on which named task or question.
- Cost — spent against estimate, if the record has it.
Be accurate rather than encouraging
- Distinguish
DONE and verified from reported done and not yet
verified. They are not the same claim and the second is worth less.
- If
check_trace reports findings, say so here. A project that looks 80%
done and has three uncovered requirements is not 80% done.
- If the last checkpoint said
DRIFTED and nothing has changed since, that is
the headline, not a footnote.
- If nothing has happened since the last status, say that plainly. Padding a
status report is how a project loses a week without anyone noticing.
1---2name: status3description: Report where a devteam project actually stands — what is running, what is blocked, what is waiting on the client, what was decided without them, and what the evidence says has genuinely been discharged. Reads the board, the record and the tree; changes nothing.4---56# Status78Answer the question **"where is it?"** honestly, from evidence, in under9twenty lines. **Change nothing** — not the board, not a title line, not a10stale claim you happen to notice. Say it is stale and let the loop recover it.1112## Read, then report1314`BOARD.md` for the live picture · the last entries of `RECORD.md` · task title15lines for real states · `git log` for what actually landed.1617```bash18python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check_trace.py" .19```2021## Report, in this order22231. **Phase and width** — onboard, plan, build, harden or deliver.242. **In flight** — each task, since when, on what model, and *what its25 supervisor last reported*. A claim with no live agent is **stale**: say so.26 **Then one line per open sandbox**, read from `devteam/.run/locks/*.sandbox`27 — task, step, id, whether the pid is live, and the root. A headless worker28 is invisible to `ListAgents` (P-14b), so without this line a task that is29 actively being worked reads here as a task with nobody on it.303. **Waiting on the client** — every open question, its class, and how long it31 has been waiting. Put this above "done" if anything is here; it is the only32 part the client can act on.334. **Decided without the client** — count, and the ones still cheap to34 reverse (P-27).355. **Progress, by evidence** — requirements `discharged` **with acceptance36 evidence recorded**, out of the total. Not tasks closed; not a percentage37 of anything. A task closed without its acceptance criterion run has not38 discharged its requirement (P-5).396. **Blocked** — what, and on which named task or question.407. **Cost** — spent against estimate, if the record has it.4142## Be accurate rather than encouraging4344- Distinguish **`DONE` and verified** from **reported done and not yet45 verified**. They are not the same claim and the second is worth less.46- If `check_trace` reports findings, say so here. A project that looks 80%47 done and has three uncovered requirements is not 80% done.48- If the last checkpoint said `DRIFTED` and nothing has changed since, that is49 the headline, not a footnote.50- If nothing has happened since the last status, say that plainly. Padding a51 status report is how a project loses a week without anyone noticing.
alternative-intelligence-cp