project-status-reportlisted
Install: claude install-skill Seneku/project-status-report
# Project Status Report
One page that collates the state of a project: what is built, how much of it there is,
what verifies it, what is dated and owed, and what is missing. Written to be read top to bottom
by someone who has not seen the project for a month — a producer, a publisher, a collaborator,
or the user themselves in six weeks.
It is a deliverable with an audience, not terminal output. Publish it as a page (see §5).
## The one rule
**Measure from the repo. Never copy numbers out of a doc.**
Status docs go stale within days of being written, and a status report that launders a stale
number into a nicer typeface is worse than no report — it makes the drift harder to catch. Every
count on the page is produced by a command run today.
When an in-repo doc disagrees with what you measured:
1. The measured value goes on the page.
2. Footnote the drift on the page, naming the doc and both values.
3. Offer to correct the doc in the same turn. Do it if the user says yes.
If a number genuinely cannot be measured (a count that only exists in a design doc, an
externally-held figure), say so in the footnote rather than presenting it as counted.
## Procedure
### 1. Gather
Read [reference/measure.md](reference/measure.md) for per-stack counting commands. Batch the
commands — this is a handful of shell calls, not an exploration.
Collect, in this order:
- **Git state.** Branch, HEAD hash, total commits, first-commit date, working-tree cleanliness,
every branch's divergen