review-for-simplicity

Reviews plans, proposals, and code changes for unnecessary complexity and premature abstraction.

3|Updated Feb 15, 2025
One-click install
npx skills add https://github.com/mark-torres10/ai_tools --skill review-for-simplicity-mark-torres10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-for-simplicity
Source: https://github.com/mark-torres10/ai_tools/tree/main/skills/review-for-simplicity
Command: npx skills add https://github.com/mark-torres10/ai_tools --skill review-for-simplicity-mark-torres10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans, proposals, and code changes often accumulate speculative abstractions, extra layers, and future-proofing that are not justified by current requirements, making them harder to build and maintain. This Skill runs a skeptical but fair review that pushes toward the smallest solution that can ship safely now. ## Core Features & Use Cases - Complexity Audit: Inventories extra models, layers, services, configuration, and orchestration, then checks whether each piece satisfies a concrete present requirement. - Evidence vs. Assumption Check: Separates explicit requirements from inferred or speculative claims before judging the design. - Simpler Alternative Proposal: Recommends exactly what to cut, merge, defer, or keep, with a verdict of acceptable, simplify first, or not justified yet. - Use Case: Before implementing a plan that adds a FeatureFlag model, resolver service, cache, and rollout strategy interface for one internal feature, run this review to get a narrower first version such as a single flag store plus one helper function. ## Quick Start Ask the assistant to review your plan or diff with review-for-simplicity and challenge whether the design is overengineered.

Frequently Asked Questions about review-for-simplicity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my implementation plan is overengineered?

Submit the plan for a simplicity review that separates explicit requirements from assumptions, inventories each added abstraction, and asks what breaks if it is removed. The output names specific excess and proposes a narrower version to ship.

How to review a pull request for unnecessary abstraction?

Run a simplicity-focused review on the diff that flags single-implementation interfaces, premature caching or retries, and coordination layers for single-path flows. It recommends concrete cuts, merges, or deferrals rather than generic advice.

When should I use a simplicity review instead of a code review?

Use it when the concern is scope and complexity, such as challenging a plan before implementation or pressure-testing a proposal. Do not use it when correctness, bugs, or security are the main concern, or for open-ended brainstorming.

What kinds of complexity does a simplicity review flag?

It flags abstractions without a second use case, multiple data models where one suffices, configuration systems for a few values, plugin frameworks without variation, and premature caching, queuing, or distribution.

What output does the simplicity review produce?

It returns a compact memo with a bottom-line verdict (acceptable, simplify first, or not justified yet), what seems solid, what seems overbuilt, a simpler version to ship, and follow-up questions only when they would change the recommendation.