From funzies
Apply YAGNI (You Aren't Gonna Need It) to a feature, plan, design, or diff: separate what is needed now from speculation and cut the rest. Use proactively when a plan includes functionality for hypothetical future requirements, configurability nobody asked for, abstractions with one implementation, or 'while we're at it' additions. Also use when someone says 'yagni', 'do we really need this', 'is this premature', or asks to trim scope.
How this skill is triggered — by the user, by Claude, or both
Slash command
/funzies:yagni [feature, plan, or code to challenge][feature, plan, or code to challenge]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Apply YAGNI to: $ARGUMENTS
Apply YAGNI to: $ARGUMENTS
If no argument is given, apply it to the plan, design, or change under discussion.
Ron Jeffries (XP): "Always implement things when you actually need them, never when you just foresee that you will need them." Speculative functionality costs now (build, review, maintenance, cognitive load) against a benefit that usually never arrives, and when it does arrive, it arrives with better information than you have today.
## YAGNI: <proposal>
| Element | Verdict | Why |
|---------|---------|-----|
| ... | Keep / Delete / Defer | one line |
### Trimmed version
<the proposal with only the Keep items>
npx claudepluginhub marjovanlier/claude-plugins --plugin funziesGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.