sm:yagni

What problem does it solve?

YAGNI prevents teams from moving into implementation based on untested assumptions by forcing a quick check for evidence and user contact before staging. It reduces wasted engineering effort, long-term maintenance costs, and product risk by ensuring decisions are grounded in observed user needs.

Core Features & Use Cases

• Gatekeeping: Intervenes when a builder proposes starting work without documented validation.
• Quick Triage: Asks one focused question to surface whether who was spoken to, what was found, and what signal justifies building.
• Actionable Outcomes: If evidence exists, the skill clears the way; if not, it offers pathways to run invalidation prep, proceed with a visible YAGNI flag, or defer to a skip when appropriate.
• Use Case: A developer suggests building feature X; YAGNI asks for validation, and either authorizes the build when evidence is provided or routes the team into an invalidation flow.

Quick Start

Ask the builder: Before we build — what did you find out, and who told you?