Identify Big Design Up Front anti-patterns in software architecture and code.
npx skills add https://github.com/messeb/skills --skill bduf
Please help me install this Agent Skill. Skill: bduf Source: https://github.com/messeb/skills/tree/main/plugins/general-developer/skills/bduf Command: npx skills add https://github.com/messeb/skills --skill bduf
This Skill helps developers distinguish between necessary upfront design and the anti-pattern of "Big Design Up Front" (BDUF), preventing wasted effort on speculative requirements and over-engineering.
Use the bduf skill to audit the current design for signs of Big Design Up Front.
High-intent search queries and answers about installing and using this skill.
Big Design Up Front (BDUF) is an anti-pattern where extensive upfront design effort is spent on speculative requirements before coding begins. It leads to over-engineering, excessive abstraction, and generic frameworks built for problems that do not yet exist.
Distinguish over-engineering from necessary design by evaluating risk. Warranted upfront design targets high-risk areas like security and APIs, while over-engineering focuses on speculative abstractions and excessive configuration that hinder iterative development.
Warning signs of over-engineering include over-abstraction, excessive configuration, and creating generic frameworks for specific problems. These code patterns indicate excessive design effort and a lack of iterative development.
Audit a proposed software feature for premature complexity by applying risk-driven design principles. Check for speculative abstractions and excessive configuration, ensuring the design balances necessary planning with iterative development.
You should invest in more upfront design instead of purely iterative development when dealing with high-risk areas like security and APIs. In these cases, upfront design is warranted to prevent critical architectural flaws.
The YAGNI (You Aren't Gonna Need It) principle helps prevent over-engineering by discouraging speculative abstractions and generic frameworks. It aligns with risk-driven design to focus development on current requirements rather than speculative features.
nishchaydevGuide architectural decisions through requirements discovery, trade-off evaluation, and ADR documentation.
roderikRefactor recently modified code for clarity while preserving behavior.
mbepsProvides architectural framework for sustainable software engineering using SOLID, DRY, KISS, and YAGNI principles.
kissrosecicd-hubIdentify dependencies with elevated risk of exploitation or takeover.
