verify-impl

原文涵盖的主题

• Verify Implementation Against Specification
• Route precisely
• Fix the authority and scope
• Compare each obligation
• Report

Compare a named implementation scope with an authoritative specification. Produce a traceable conformance verdict without editing code, tests, or the specification. Respond in chat unless a report file is explicitly requested. Use this skill only when a specification and an implementation are both in scope and the user asks whether the code fulfills the spec. Use review-spec to assess a spec before implementation. Use review-arch to assess system structure without a requirement-by-requirement contract. Use code-review to find defects introduced by a diff; that review may cite a spec but does not imply exhaustive conformance. Use plan-review for a proposed implementation plan. 1. Identify the exact spec file or revision and the implementation paths, module, commit, or PR being checked. If either side is unavailable, report what is missing before assigning a verdict. 2. Read applicable repository instructions, binding architecture decisions, and the spec in full. Note conflicts between sources rather than silently choosing one. Treat an explicitly superseded spec as historical, not authoritative. 3. Extract each independently verifiable obligation into a stable ID. Preserve a short e

这里只展示节选，请以完整原文和当前要求为准。