Spec Alignment

Use this skill to sanity-check whether work matches intent.

When Invoked

Good fit when:

• requirements are spread across multiple messages/files;
• a large change needs a quick "did we build the right thing?" pass;
• review or test signals conflict on expected behavior.

Inputs

Use whichever requirement sources are available, typically:

• explicit user instructions;
• plan/spec docs (plans, ADRs, acceptance notes);
• tests that encode intended behavior;
• recent implementation/review reports.