<< All versions

Skill v1.0.1

currentAutomated scan100/100
auditmos/brainstormer/lean
──Details
PublishedSeptember 27, 2026 at 02:16 AM
Content Hashsha256:f0273a9a30b43bec...
Git SHA011caf8fe23a
──Files
Files (1 file, 2.5 KB)
SKILL.md2.5 KBactive
SKILL.md · 83 lines · 2.5 KB

name: lean version: 1.0.1 description: Enforces MVP development principles — speed over perfection, utility first, simplicity. Use proactively when planning features, architecting solutions, reviewing code, or evaluating technical decisions to prevent over-engineering.

Core Rules

RuleTest
Speed > Perfection"Ugly but useful" ships; perfect never does
Utility Firstv1.0 = "not-stupid", not brilliant
One Task RuleHandles one complete process A→Z
5-Min TestNeeds 5 tools to launch → dead; works in 5min → chance
No Over-EngineeringBuild minimum needed, nothing more

Development Approach

  • Granular tasking: small specific tasks, not essays
  • Iterative: Task → Build → Test → Repeat (not spec-driven)
  • AI as accelerator: 3x faster, not replacement
  • Founders code: keep "feel" for product

Architecture Principles

  • Use ready-made for logging/billing/auth — focus effort on value
  • Open-Closed: extend via overlays, don't fork core
  • Security proportional to data sensitivity

When Invoked

  1. Read the proposed solution or code
  2. Flag over-engineering against core rules
  3. Check for unnecessary complexity
  4. Verify it solves one complete task A→Z
  5. Verify 5-minute launchability

Red Flags

  • Too many abstractions for current needs
  • Premature optimization
  • Feature bloat beyond the one task
  • Complex setup process
  • Not solving own problem first

Output Format

Over-engineered: [specific issues found]
Simplify to: [concrete alternatives]
MVP path: [minimum implementation to ship]

Skip sections with no issues. Be direct — "this is fine" if nothing to flag.

Examples

Over-engineered input

"We need a plugin system with dependency injection, event bus, and config schema validation for our MVP notification feature."

MVP response

Over-engineered: Plugin system + DI + event bus for a notification feature. Three abstractions for one task.
Simplify to: Single function that sends notifications via one channel.
MVP path: `sendNotification(userId, message)` → hardcode email provider → ship today, add SMS/push when users ask.

Clean input

"Add a /health endpoint that returns 200."

MVP response

Clean. One task, ships in 5 minutes, no abstractions.

Acceptance checklist

  • [ ] Reviewed proposed solution against core rules
  • [ ] Flagged specific over-engineering issues (if any)
  • [ ] Provided concrete simplification alternatives (if needed)
  • [ ] Verified one-task completeness
  • [ ] Verified 5-minute launchability
All versions