Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Mvp Scope Killer

ASecurity

Cuts premature over-engineering from an MVP plan (microservices, custom RBAC, in-house dashboards, hand-rolled auth, speculative abstractions) into a lean core. Use when the user says /scope-kill, 'cut scope', 'is this overkill for an MVP' or 'what can we drop'.

3 stars
0 votes
0 copies
0 views
Added 10/2/2026
ai-agentssqlnextjsfastapikubernetesapi

Works with

api

Security Analysis

A100/100

Scanned 10/2/2026

$npx -y skills add Gastonchevarria/god-mode --skill mvp-scope-killer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mvp Scope Killer?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Mvp Scope Killer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gastonchevarria-mvp-scope-killer/badge)](https://www.skillsdirectory.com/skills/gastonchevarria-mvp-scope-killer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: mvp-scope-killer
description: "Cuts premature over-engineering from an MVP plan (microservices, custom RBAC, in-house dashboards, hand-rolled auth, speculative abstractions) into a lean core. Use when the user says /scope-kill, 'cut scope', 'is this overkill for an MVP' or 'what can we drop'."
---

# MVP Scope Killer

## Overview

The death of startups is rarely a lack of features; it is almost always building too much before validating the core transaction. `mvp-scope-killer` acts as an aggressive scope editor, eliminating 50% to 80% of unnecessary complexity from initial roadmaps.

## The Scope Guillotine (What to Kill Immediately)

When reviewing any plan or feature list, actively detect and kill:

1. **Premature Microservices & Distributed Infrastructure**:
   - *Kill*: Splitting a new MVP into 5 microservices, Kafka queues, and Kubernetes.
   - *Replace With*: Clean modular monolith on Next.js/FastAPI + PostgreSQL.
2. **Elaborate Role-Based Access Control (RBAC)**:
   - *Kill*: Building granular 7-level permission matrices for an app with 0 users.
   - *Replace With*: Single `admin` vs `member` boolean flag.
3. **Vanity Analytics Dashboards**:
   - *Kill*: Custom BI charts and analytics suites that the founder wants to build in-house.
   - *Replace With*: Embedded PostHog / Mixpanel snippet or simple raw query table.
4. **Complex Custom Authentication**:
   - *Kill*: Hand-rolling OAuth, SMS 2FA, and password reset tokens from scratch.
   - *Replace With*: Supabase Auth, Clerk, NextAuth, or Firebase Auth.
5. **Speculative Abstractions & Generic Frameworks**:
   - *Kill*: Designing a generic multi-tenant plugin system before building the first plugin.
   - *Replace With*: Direct, straightforward code. Refactor only upon the 3rd concrete use case (Rule of Three).

## Scope Killer Report

Produce `brain/<conversation-id>/mvp_scope_pruning.md`:

```markdown
# MVP Scope Killer Report

## Original Scope Breakdown
- [Feature 1]
- [Feature 2]
...

## ✂️ Pruned Items (Moved to Post-PMF Backlog)
- **Killed**: [Complex Item 1] -> **Reason**: [Premature complexity]
- **Killed**: [Complex Item 2] -> **Reason**: [No direct impact on initial conversion]

## ⚡ Remaining Lean MVP Core (Shippable in < 48-72h)
1. [Atomic Flow Step 1]
2. [Atomic Flow Step 2]
3. [Atomic Flow Step 3]
```

Attribution

GastonchevarriaGastonchevarria
View sourceSee grades on GitHubMore from Gastonchevarria →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →