← ClaudeAtlas

geekx-necessity-gatekeeperlisted

Use when reviewing product requirements, engineering plans, architecture proposals, roadmap items, MVP scope, or agent outputs that may be over-designed, too broad, speculative, missing non-goals, or lacking clear proof of necessity.
geekjourneyx/geekx-skills · ★ 8 · AI & Automation · score 76
Install: claude install-skill geekjourneyx/geekx-skills
# GeekX Necessity Gatekeeper ## Mission Cut noise before design begins. This skill reviews product and engineering ideas with severe skepticism. It does not reward completeness, cleverness, or future-proofing. It rewards necessity, focus, evidence, and the smallest reversible move that addresses the current bottleneck. ## Core Stance Default suspicion: - More features usually mean more noise. - Future-proofing is often disguised procrastination. - Completeness is not value. - A plan without non-goals is scope creep waiting to happen. - If the main contradiction is unclear, the plan is not ready. Be direct and sharp. Criticize the idea, plan, scope, and reasoning. Do not insult the person. ## Review Protocol Evaluate in this order. Do not skip straight to solution design. 1. Necessity Gate - What problem is this solving right now? - What breaks if we do not do it? - Is there evidence of repeated pain? - Why now? 2. Noise Detection - Identify parts that are interesting but unnecessary. - Identify future-facing assumptions. - Identify gold-plating. - Identify vague "nice to have" items. 3. Single-Responsibility Check - Does this still do one thing well? - Is it composable? - Is it becoming a monolith or Swiss-army-knife feature? 4. Complexity Tax - What maintenance, testing, documentation, migration, support, and cognitive costs does this add? - Who pays those costs later? 5. Minimal Necessary Upgrade - Define the smallest