scope-hammer

Classify brainstorm ideas into DELETE, MOCK, ALREADY EXISTS, or SHIP categories.

3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/carlkibler/agent-skills --skill scope-hammer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-hammer
Source: https://github.com/carlkibler/agent-skills/tree/main/skills/scope-hammer
Command: npx skills add https://github.com/carlkibler/agent-skills --skill scope-hammer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Brainstorm outputs often contain too many ideas, making it hard to identify what to build first, delaying progress and causing scope creep.

Core Features & Use Cases

  • Idea Classification: Automatically categorize brainstorm items into DELETE, MOCK, ALREADY EXISTS, or SHIP to streamline decision-making.
  • Scope Simplification: Help teams focus on essential features for a minimal viable product by reducing scope complexity.
  • Use Case: After generating a long list of potential features, use this skill to quickly narrow down to the most impactful subset for launch.

Quick Start

Ask the AI to classify a list of features from your brainstorm or backlog to identify what to cut, fake, or build first.

Frequently Asked Questions about scope-hammer

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

FAQPage Schema
How do I prioritize features for an MVP from a large brainstorm list?

To prioritize features for an MVP, you can classify each brainstorm item into categories like DELETE, MOCK, ALREADY EXISTS, or SHIP. This scope reduction method identifies essential features for rapid release while aligning with technical constraints.

What is the best way to reduce product scope and prevent scope creep?

Reducing product scope effectively involves classifying feature ideas into DELETE, MOCK, ALREADY EXISTS, or SHIP categories. This strategy simplifies decision-making and helps teams focus only on essential features for a minimal viable product launch.

How do I classify a backlog to identify what to cut, fake, or build?

You can classify a backlog by analyzing feature lists and assigning each item to DELETE, MOCK, ALREADY EXISTS, or SHIP. This classification process clarifies what to cut, fake, or build first for efficient MVP scope definition.

Can I use automated idea classification for rapid release preparation?

Yes, automated idea classification analyzes brainstorm outputs to categorize features into DELETE, MOCK, ALREADY EXISTS, or SHIP. This enables rapid release preparation by ensuring decisions align with technical and strategic constraints.

When should I use MOCK versus SHIP categories for MVP features?

Use the MOCK category for MVP features that can be faked or simulated to test concepts without full build effort, while SHIP identifies essential features requiring actual development. This distinction streamlines scope reduction for rapid release.