atmos-specs-reviewlisted

# Atmos Specs Review This skill turns a post-implementation review into durable, actionable `REVIEW.md` entries. It is for checking shipped code against a spec and recording fix status; it is not a requirements-writing skill and it does not implement fixes unless the user explicitly asks to continue into implementation. ## Mode selection Pick the smallest review mode that answers the user's request. | User asks for... | Load | |------------------|------| | Functionality, completeness, spec coverage, PRD/TECH/TEST alignment, behavior, acceptance, regressions, user flows | [`references/functional-review.md`](./references/functional-review.md) | | Architecture, maintainability, code size, layering, duplication, testability, reliability, security, performance, "non-functional" quality | [`references/quality-review.md`](./references/quality-review.md) | | "review it", "is this done", "ready to ship", "functionality and code quality", or anything ambiguous after implementation | Both references | If the user asks to fix existing `REVIEW.md` findings rather than review, read `REVIEW.md` first, update statuses as you work, and use the relevant reference only to validate that the fixes are complete. ## Read order 1. Root `AGENTS.md` for repository architecture, transport rules, and workflow. 2. `specs/AGENTS.md` for `REVIEW.md` conventions and template location. 3. The target spec directory: - `PRD.md` for product intent and Must Have scope. - `TECH.md` for the intended a