Amby Review

Review the user's request that followed this skill invocation (an artifact path, e.g. specs/NNN-slug/spec.md) as a different role. If the path does not exist, stop and name the phase that produces it.

1. Pick the reviewer: --as <id> → @.amby/roles/<id>.md; otherwise QA for a spec or tasks, Architect for a plan, PM for a UI design. If the file is missing, stop and list .amby/roles/. Say which role you are acting as in your first line.
2. Read only the artifact (and its spec, if reviewing a plan or tasks). Apply the role's focus checklist. Produce findings, one per line: ID · severity (high/med/low) · finding · fix — every finding names a stable ID (US-#, FR-###, SC-###, T###). Modify nothing.
3. Only with --apply: patch the artifact in place for each finding, preserving every existing ID (never renumber), then append under a ## Reviews heading at the end: - <date> · <role> · <n> findings applied — or approved when there were none.
4. This is advisory: no phase waits on a review. End with the findings count and the next phase to run.