check-impl-against-spec

Compare PR code against BMO technical specifications to identify deviations and risks.

2|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/codysumpter-cloud/buddy-brain --skill check-impl-against-spec-codysumpter-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-impl-against-spec
Source: https://github.com/codysumpter-cloud/buddy-brain/tree/main/.agents/skills/check-impl-against-spec
Command: npx skills add https://github.com/codysumpter-cloud/buddy-brain --skill check-impl-against-spec-codysumpter-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps prevent scope creep and potential risks by ensuring that Pull Request (PR) implementations are in alignment with their referenced BMO technical specifications.

Core Features & Use Cases

  • Spec Alignment Check: Verifies that PRs meet the technical requirements outlined in BMO tech specs.
  • Risk Identification: Identifies gaps, risks, and verification status of PR implementations.
  • Use Case: Before merging a PR, this Skill can be used to ensure that the implementation meets the specified standards, thus maintaining code quality and consistency.

Quick Start

Run the check-impl-against-spec skill to compare the current PR implementation against the BMO tech spec 'tech-spec-v1.md'.

Frequently Asked Questions about check-impl-against-spec

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

FAQPage Schema
How do I check if a PR implementation aligns with a tech spec?

To check PR implementation alignment with a tech spec, compare the pull request code against the referenced technical specification to identify deviations, verify requirements, and flag integration risks before merging.

What is spec compliance review in code reviews?

Spec compliance review in code reviews is the process of verifying that pull request implementations adhere to technical specifications, preventing scope creep by identifying gaps between the written requirements and the submitted code.

Can I identify scope creep risks before merging a pull request?

Yes, you can identify scope creep risks before merging a pull request by comparing the PR implementation directly against the BMO tech spec to detect unauthorized feature additions and requirement deviations.

What's the best way to verify BMO tech spec requirements in a pull request?

The best way to verify BMO tech spec requirements in a pull request is to run an automated spec alignment check that compares the PR code against the tech spec file to highlight gaps and verification status.

Do I need a tech spec file to review PR code for spec compliance?

Yes, you need a referenced tech spec file such as 'tech-spec-v1.md' to review PR code for spec compliance, as the Skill requires a baseline technical specification to compare the implementation against for deviations.