← ClaudeAtlas

review-speclisted

Review proposed specifications for feasibility, gaps, and testability; not plans or code conformance.
ValentinNikolaev/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill ValentinNikolaev/agent-skills
# Review Specification Review a proposed design or requirements document before it becomes an implementation contract. Return an evidence-backed readiness verdict without editing the document or creating a report file unless requested. ## Route precisely - Use this skill when the primary question is whether a proposed specification or design revision is sound. Related code may already exist; inspect it as context without turning this into a code review. - Use `plan-review` when the primary artifact is an ordered implementation plan. - Use `verify-impl` when the question is whether existing code satisfies an authoritative specification. - Use `review-arch` for the structure of an existing system or a system-wide architecture decision. - Use `code-review` for changed code or a pull-request diff. ## Scope and economical inputs Own requirement coverage, consistency, explicit obligations, operator walkthroughs for proposed screen changes, and testability. Not my scope: ordered implementation steps, step-by-step worst-case timing/capacity arithmetic (`plan-review`), component-boundary redesign and competing architecture alternatives (`review-arch`), or line-level code defects (`code-review`). Check that ownership and failure requirements are specified without repeating those specialists' analyses; name a needed follow-up without starting another review automatically. Accept `shared_context=PATH` containing already-collected code facts, paths, excerpts, schemas, and their sour