VISION.md triage verdict

If the repository has a VISION.md on the default branch, read that file in full before any final triage decision. If it does not exist, skip this skill.

Do not special-case a repository. The file in front of you is the only source of rules.

Rules

Treat each ## heading in VISION.md as one rule. If there are no ## headings, treat the document as a single rule named after the # title, or as VISION.md if that is also missing.

For every rule, return exactly one of:

• aligns — the change or issue follows that rule. Cite the evidence.
• does not align — the change or issue conflicts with that rule. Cite the evidence.
• cannot tell — the text of the rule, the change, or both are insufficient. Cite what is missing.

Claims are not enough. A PR title, issue pitch, or author summary does not count as evidence. Read the actual diff, the actual issue body plus the code or docs it names, and the rule text.

Cannot-tell blocks auto-merge. Any rule that is cannot tell, inconclusive, or undecided is no verdict: do not auto-merge, do not close as decided on that rule. Flag Firstmate or stop. Do not ignore some undecided rules. Do not coerce cannot tell into aligns or does not align. Do not invent a matching heading. Do not skip a heading.