Triage Findings

Bridge between a findings report (from prd-self-audit pre-implementation, or a code review post-implementation) and the right downstream action. For each finding, classify into one of four buckets and name what happens next.

This skill produces a report. It does NOT edit the PRD, open issues, or invoke grill-with-docs / to-issues. Those are downstream decisions for the user.

Inputs

1. A findings report — Markdown. Either an audit report (sections: Contradictions / Missing invariants / End-to-end walkthroughs) or a review report (any structure; bug-style findings against a branch). The shape varies; treat each bullet/heading as one finding.
2. A PRD path — the document each finding is being judged against.

If the report references ADRs, migrations, accepted follow-up issues, or a CONTEXT.md, read those too. The "PRD is right / PRD is wrong / design moved" call often hinges on what an artifact next to the PRD already says.

Process

Read the report and the PRD end-to-end first. Then, for each finding, apply this rule:

Would a fresh reader of the PRD now reach a different conclusion than the code (or the report's claim)? If yes → amend. If the design itself has moved → re-grill that section only. If the PRD is right and the code is wrong → new issue. If neither has moved and the PRD already implies the answer → no-op.