status

name	status
description	Read-only progress report of a PRD-planned project — status counts, what is building, what is ready to start, what is blocked, and drift against the tracker if issues are linked.
argument-hint	[optional: path to the PRD folder]

/prd:status — where is the project?

Read-only. Parses the frontmatter of every WP-*.md (folder from $ARGUMENTS or auto-detected: docs/prds/, docs/PRD/, prds/) and reports. It writes nothing and changes nothing.

Report (in this order)

1. Headline — one sentence: X of N WPs done · Y building · Z ready to start.
2. Building now — WPs with status: building, each with owner and how long the header says it's been open if inferable from git (git log --follow -1 --format=%cs on the file when it moved to building is a good proxy; skip if not a git repo). If more than ~2 WPs are building at once, point it out — WIP limits exist for a reason.
3. Ready to start — not-started WPs whose dependencies are all done:
   • specified → ready to build now.
   • skeleton → needs /prd:fill first; say so explicitly.
4. Blocked — WPs that cannot start: which dependency (or external blocker) is holding each one. Highlight blockers sitting on the critical path (heaviest dependency chain, size-weighted S=1/M=2/L=3).
5. Skeleton debt — skeletons whose dependencies are all done or building: these should be filled soon, before they block the flow.
6. Tracker drift (only if issue: fields are populated and a tracker tool, e.g. Linear MCP, is available) — compare each WP's status with its issue's state and list mismatches. Convention: the tracker wins — it is what the whole team sees. Offer to fix the frontmatter to match (that edit needs explicit confirmation, since this command is otherwise read-only).

Close with the suggested next action, e.g. "fill WP-07 (/prd:fill WP-07) — it is on the critical path and its dependencies are done" or "refresh the map (/prd:map), the frontmatter changed since it was generated".