rfc-status

# /rfc-status Surface the current RFC landscape in one pass. Useful at session start (with `workspace-status`) or any time you need to know what governance work is in flight before proposing or opening a new RFC. ## Output rendering Table — When presenting several items that share the same fields, render a Markdown table. Cap at ~5 columns; beyond that, switch to a per-item detail list. Right-align numeric columns. ## When to invoke Any request for an RFC overview: "what RFCs are active?", "rfc status", "show me open rfcs", "how many rfcs do we have?", "any rfc candidates?". Also runs as a sub-step of `workspace-status` to populate the findings count line. ## Procedure ### 1. Scan `docs/rfc/*.md` Read every `.md` file in `docs/rfc/`. For each file, extract the `**Status:**` front-matter line. The valid lifecycle states per CONVENTIONS.md §3 are: ``` Draft | Open | Final Comment Period | Accepted | Rejected | Withdrawn | Experimental | Superseded ``` `Shipped` is a spec status, not an RFC status — if encountered, treat as unrecognised and surface in a `⚠ Unrecognised status` group. Group results by state. Within each group, list RFCs as: `RFC-NNNN: <title>` (derive title from the first `# RFC-NNNN: …` heading). ### 2. Scan `docs/product/findings/rfc-candidates.md` If the file exists, count the non-header data rows in the register table (rows that are not the separator `|---|…` row or the header row). Surface the count separately — this is not a lifecycle state but...