over-engineer-no-more

Over-Engineer No More

Overview

After planning but before execution, evaluate whether the implementation is trivial enough to execute directly rather than using heavyweight processes.

Core principle: Match execution process to implementation complexity. Don't launch 33 subagents to add items to arrays.

When to Use

Use this skill:

• After writing an implementation plan
• Before launching subagent-driven development
• Before launching a multi-step execution workflow
• When user says "just add..." or "simple change..."

Always check complexity before heavyweight execution.

The Triage Process

Step 1: Analyze the Plan

Ask these questions:

Trivial Implementation Indicators:

• Just adding constants, enums, or items to arrays/lists?
• No new functions or types being created?
• No new business logic or algorithms?
• Just updating data structures + corresponding tests?
• Estimated < 100 lines of actual code?
• Changes confined to < 3 files?
• All changes are in the same package/module?

If 3+ indicators are TRUE -> This is trivial

Step 2: Announce Decision

For Trivial Implementation:

Plan complete. Checking execution complexity...

Changes required:
- [List specific changes from plan]

This is trivial implementation (adding items to lists/updating data).

I'll implement directly rather than using subagent-driven development.
This will:
- Save time (10 min vs hours)
- Use fewer credits (1 agent vs 33)
- Produce the same quality result

Proceeding with direct implementation.

For Complex Implementation:

Plan complete. Checking execution complexity...

Changes required:
- [List specific changes from plan]

This is complex implementation requiring:
- New business logic / algorithms
- Multi-file coordination
- Database migrations / API changes

I'll use subagent-driven development for:
- Fresh context per task
- Thorough review cycles
- Quality verification

Proceeding with subagent-driven development.