Implementation Alignment Review

Context

This skill checks whether the implementation actually satisfies the user's intent and approved scope. It exists because green tests, a plausible summary, or a working happy path can still hide a mismatch between requested outcome, implemented behavior, documentation, and delivery claims.

Use it before broad code review when the main risk is not style or local correctness, but whether the delivered artifact is the right artifact.

Inputs

• intake-brief: The original intent, target context, non-targets, and evidence expectations.
• task-list: The approved implementation slice and any priority ordering.
• acceptance-criteria-set: The explicit pass/fail contract, including negative criteria.
• source-code: The diff or implementation surface.
• test-suite: Tests, fixtures, snapshots, smoke logs, and validation output.

Also read requirements docs, specs, architecture notes, runbooks, or quality snapshots when they are referenced by the task.

Process