check-alignment

Audit codebases against product specs and architecture decisions.

41|4|Updated Jan 28, 2026

Search Tags:#architecture #alignment #drift-detection #quality-assurance #prd #code-review #spec-comparison

Ready to run

npx skills add https://github.com/etr/groundwork --skill check-alignment

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-alignment
Source: https://github.com/etr/groundwork/tree/main/skills/check-alignment
Command: npx skills add https://github.com/etr/groundwork --skill check-alignment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that implementation aligns with product specs and architecture, surfacing misalignments for resolution.

Core Features & Use Cases

Drift detection and alignment reports between specs and code
Automated checks against architecture decisions and PRD
Review-ready outputs highlighting mismatches and suggested fixes

Quick Start

Run an alignment check against the active project to surface drift between specs and code.

Frequently Asked Questions about check-alignment

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

FAQPage Schema

How do I detect drift between product specs and my codebase?▼

Drift detection between product specs and your codebase is performed by auditing the implementation against PRD requirements and architecture decisions. It flags undocumented features and returns a structured alignment report highlighting mismatches for resolution.

Can I run architecture alignment checks on a monorepo?▼

Architecture alignment checks can be run on a monorepo. The audit evaluates multi-repo projects and monorepos during code reviews to ensure implementation matches architecture decisions and product specs, returning review-ready outputs.

What is the best way to verify code matches PRD requirements during a review?▼

The best way to verify code matches PRD requirements is to run an automated alignment check during code reviews. It evaluates the implementation against product specs and architecture decisions, then returns a structured report highlighting mismatches and suggested fixes.

How do I flag undocumented features in a multi-repo project?▼

Undocumented features in a multi-repo project are flagged by auditing the codebase against PRD requirements and architecture decisions. The process surfaces misalignments between the specs and the code, returning a structured alignment report for resolution.

Does spec comparison work for design audits across multiple repositories?▼

Spec comparison works for design audits across multiple repositories. The audit evaluates the implementation against architecture decisions and PRD requirements, flagging drift and returning a structured alignment report highlighting mismatches.