review-implementation

Reviews implementation against authoritative specifications across seven canonical review areas.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill review-implementation-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-implementation
Source: https://github.com/alvis/.agents/tree/main/plugins/specification/skills/review-implementation
Command: npx skills add https://github.com/alvis/.agents --skill review-implementation-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Verifying that finished code actually matches its approved specification is hard: specs drift, tasks go stale, and findings get duplicated or lost across review passes. This Skill runs one independent holistic review that checks implementation against the authoritative specification and coordinates all seven canonical review areas (alignment, correctness, security, quality, testing, docs, style) with stable finding identities and reconciled dispositions. ## Core Features & Use Cases - Specification alignment review: Traces spec-to-code for omissions and drift, and code-to-spec for unsanctioned behavior, binding every verdict to the exact approved specification content and task definitions. - Freshness-gated Notion sources: Invokes sync-spec materialization as a mandatory pre-review probe so reviews never run against stale external specifications. - Disposition lifecycle management: Applies open, fixed, acknowledged, deferred, and skipped dispositions with severity rules (P0-P3) and stable ALIGN-P<n>-<seq> finding IDs that survive reruns. - Use Case: After implementing a feature from a Notion spec, run the review to confirm every success criterion is covered, get per-area verdicts, and reconcile any drift findings with the user before closing the work item. ## Quick Start Ask the agent to review the current implementation against the approved specification for the active work item and summarize dispositions across all review areas.

Frequently Asked Questions about review-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review implementation against a specification?

Invoke the review with the active work item resolved; it reads the authoritative specification, traces requirements to code in both directions, and returns per-area verdicts with cited findings. Alignment findings use stable IDs so reruns preserve prior reconciliation.

What review areas does specification alignment checking cover?

Seven canonical areas: alignment, correctness, security, quality, testing, docs, and style. Alignment owns contract conformance, correctness owns spec-independent bugs, and correctness plus security coverage is mandatory on every completed review.

Can I review code against a Notion specification?

Yes, but the review requires a mandatory sync-spec materialize freshness probe before dispatch and again before finalization. If the remote spec changed structurally, the review returns needs_revalidation instead of emitting a stale verdict.

Why does a review return needs_revalidation or ready_for_specification?

ready_for_specification means no authoritative specification could be resolved or provenance drifted. needs_revalidation means the spec content or task definitions changed after review, invalidating findings bound to the earlier inputs.

What are the limitations of the alignment review?

The review is read-only with respect to implementation and never writes state itself; the main agent persists area reports and the summary. It also refuses to run without a verified authoritative specification and current correctness and security evidence.