What problem does it solve? Architecture rules written in a project charter often stay as prose that nobody enforces, so layering violations, dependency cycles, and forbidden patterns creep into the codebase unnoticed. This Skill turns the charter's architecture section into an objective, tool-verified gate at Checkpoint 7 of the DAE pipeline. ## Core Features & Use Cases - Architecture fitness check: Runs dae_arch.py against the manifest's architecture rules to detect layering violations, dependency cycles, forbidden patterns, file naming issues, and oversized files. - Pipeline gating: Verifies prior checkpoints and branch hygiene before running, and blocks Checkpoint 7 completion until violations are resolved. - Runbook verification: Cross-checks runbook.md blocking steps against deploy-related acceptance criteria to surface verification gaps. - Use Case: After implementing a feature, run the check to confirm the new code respects the charter's dependency layering before handing off, then triage each violation with the human as either a code fix or a charter amendment. ## Quick Start Ask the agent to run an architecture check on the current feature to verify the code follows the charter's layering and dependency rules.
