Coordinate findings work with the user, decide whether scan, test, or sync should run, and turn the current findings set into a ready plan. Accept optional `path` and GitHub PR `url`; default to `path=infer`. Confirm effective variables before starting.
Read these shared references when needed:
../shared/references/findings.schema.md../shared/references/findings.lifecycle.mdTriage is the planning and clarification layer across findings work.
scan-codebase, test-codebase, sync-findings, or resolve-findings.Accept an optional GitHub PR url from the prompt.
sync-findings.Default:
url=local-onlyAccept an optional path from the prompt.
path is provided, use it as the local design or findings folder.path is omitted, infer it from the branch, subsystem, or matching docs and state the inferred value before starting.Default:
path=inferEstablish triage scope. Confirm the effective variables first:
pathurlLoad the active findings record.
Use path/findings.md.
Decide what is missing. Determine whether the next need is:
scan-codebasetest-codebasesync-findingsresolve-findingsSurface decisions and blockers. Present open questions, competing fix paths, policy ambiguity, and missing confirmations clearly. If the user has already started answering, ask the next concrete follow-up questions in the same turn.
Produce a ready plan. End triage with a concrete next step, not a vague status-only handoff.
open or needs-user-decision.