# Requirements Report Format

All requirements review agents return results as structured markdown.

## Expected Sections

### Check Results

A table with one row per check performed. Columns vary by agent type but always include:

- **Status**: `pass` (no issues), `fail` (significant issue), or `warn` (minor concern)
- **Detail**: Human-readable description of the finding

### Recommendations

A numbered list of actionable suggestions, grouped by priority:

- **critical**: must fix before proceeding to implementation planning
- **high**: should fix, may cause issues downstream
- **medium**: recommended improvement
- **low**: nice to have

### Summary

A summary table with aggregate counts: total checks, passed, failed, warned.

## Router-Level Severity and Verdict

The router (SKILL.md Step 3) assigns severity to each non-pass finding after collecting all agent results. Agents do NOT assign severity — they only report `status` and `detail`.

The router classifies each finding as:

| Severity   | Meaning                                                                                     | Examples                                                                                 |
| ---------- | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| `critical` | Blocks progress — fundamental design flaw, missing required capability, or boundary violation | Missing entity ownership, overlapping CRUD with another module, broken state machine      |
| `major`    | Should fix — will likely cause issues downstream but not a design blocker                    | Missing standard ERP state, unclear dependency direction, incomplete business rules       |
| `nit`      | Nice to have — cosmetic, stylistic, or minor improvement suggestion                         | Naming convention preference, optional field suggestion, documentation wording improvement |

Verdict rule:

- **APPROVED**: zero `critical` and zero `major` findings (nits only, or all pass)
- **NEEDS CHANGES**: one or more `critical` or `major` findings

When verdict is APPROVED with nits, list the nits as informational notes — they do NOT block the review.
