speckit-architecture-guard-violation-detection

Detect architecture violations using framework-agnostic boundary, contract, dependency, and security-governance rules.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-architecture-guard-violation-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-architecture-guard-violation-detection
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-architecture-guard-violation-detection
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-architecture-guard-violation-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents architecture violations by systematically detecting drift between intended specifications and what is actually planned or implemented.

Core Features & Use Cases

  • Evidence-based violation detection: Flags architectural drift with concrete implementation evidence such as file paths, line numbers, or code patterns (or explicitly notes when evidence is missing).
  • Framework-agnostic governance checks: Detects intent divergence, boundary/layering erosion, contract inconsistencies, coupling issues, and Constitution/security breaches without being tied to a specific stack.
  • Targeted scopes via focus modes: Runs narrowed checks for db, api, or async boundaries to isolate the most relevant architectural risk area.

Quick Start

Run the speckit-architecture-guard-violation-detection skill with mode=architecture and focus=general to produce a categorized list of architectural violations with supporting evidence.

Frequently Asked Questions about speckit-architecture-guard-violation-detection

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

FAQPage Schema
How do I detect architecture violations and specification drift in my codebase?

You can detect architectural drift by running the architecture guard with mode=architecture and focus=general, which produces a categorized list of violations with supporting evidence such as file paths and code patterns.

What is architectural drift and how does boundary analysis identify it?

Architectural drift occurs when implementations diverge from intended specifications. Framework-agnostic boundary analysis identifies this by checking layering, coupling, and contract rules against actual code artifacts.

Can I run architecture governance checks for specific areas like database or API boundaries?

Yes, targeted focus modes support db, api, and async boundary scopes, running narrowed governance checks to isolate the most relevant architectural risk areas for specification compliance.

Does violation detection work without being tied to a specific framework or tech stack?

Yes, governance checks are framework-agnostic, detecting intent divergence, boundary erosion, contract inconsistencies, and coupling issues without being tied to a specific technology stack.

How are security architecture conflicts handled during specification compliance checks?

Security architecture conflicts are routed for critical governance review, while the detection process maintains strict read-only behavior and assigns severity levels to all evidence-backed findings.