complexity-guard

Audit design documents for over-engineering by checking them against a predefined blacklist of anti-patterns, YAGNI violations, and excessive dependencies to enforce simplicity. The skill reviews architectural proposals and assigns a complexity score to output a clear APPROVE or REJECT verdict.

YAGNI violation detection identifies speculative features and unjustified dependencies in technical proposals, stopping resume-driven development patterns. It acts as a gatekeeper to ensure new architecture adheres to the principle of least complexity before design merges.

Yes, you can review an architecture overview file before merging a new feature by passing the specific design document path to the skill. It audits the proposed architecture against common design flaws to prevent introducing unnecessary complexity into the project.

Check if a technical proposal introduces excessive dependencies by running an anti-pattern detection audit on the design file. The skill evaluates dependency management against a blacklist of design flaws and returns a complexity score to determine if the additions are justified.

A limitation of automated anti-pattern detection for RFC auditing is that it requires a review of specific design files against a predefined list of anti-patterns. It cannot dynamically discover novel architectural flaws outside its established blacklist or evaluate undocumented design rationale.