yagni-principle

What problem does it solve?

Developers often implement features or abstractions "just in case" they might be needed later, leading to wasted effort, delayed delivery of actual value, and increased code complexity (carry cost). This skill enforces the YAGNI principle to prevent over-engineering.

Core Features & Use Cases

• Feature Request Evaluation: Guides the assessment of whether functionality is required now by a current user story, or if it's speculative.
• Code Review Red Flags: Identifies anti-patterns like "Impl" classes, premature feature building, speculative abstractions, and unused configuration options.
• Cost Analysis: Quantifies the "three costs" of YAGNI violations: cost of building, cost of delay, and cost of carry.
• Use Case: You're reviewing a feature request or a code change and need to determine if the proposed functionality is truly necessary for the current sprint.

Quick Start

"Evaluate this new feature request using the YAGNI principle." "Review this code for any speculative implementations or over-engineering."