occam

Inventory project plans, test essentiality, and categorize keeps, cuts, and defers.

4|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/satsilem/claude-skills-pantheon --skill occam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: occam
Source: https://github.com/satsilem/claude-skills-pantheon/tree/main/skills/occam
Command: npx skills add https://github.com/satsilem/claude-skills-pantheon --skill occam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cuts scope and eliminates over-engineering by forcing a minimal viable solution, helping teams avoid feature bloat and scope creep.

Core Features & Use Cases

  • Inventory the plan and enumerate all components (features, modules, constraints, and edge cases).
  • Apply the essentiality tests (what breaks if removed, hypothetical vs real needs, and cost vs value) to decide keep, cut, or defer.
  • Propose a simplified version and iterate with the user until a committed, lean scope is reached.

Quick Start

Provide your current plan and I will return a lean MVP scope with keeps, cuts, and defers.

Frequently Asked Questions about occam

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

FAQPage Schema
How do I reduce project scope to ship a lean MVP?

To reduce project scope and ship a lean MVP, you inventory all planned components, apply essentiality tests to evaluate cost versus value, and categorize items to keep, cut, or defer. This eliminates feature bloat and controls complexity.

What is the best way to prevent scope creep during sprint planning?

Preventing scope creep during sprint planning requires applying essentiality tests to identify hypothetical versus real needs. By evaluating what breaks if a feature is removed, you can prune project plans to their minimal viable scope and defer non-essential modules.

How do I decide which features to cut or defer for an MVP?

Deciding which features to cut or defer for an MVP involves running an essentiality test on your project inventory. You evaluate each component by what breaks if removed, its cost versus value, and whether it addresses a real need to reach a committed lean scope.

Can I use this approach for architecture reviews and feature planning?

Yes, you can use this essentiality testing approach for architecture reviews, sprint planning, and feature reviews. It inventories modules and edge cases, then applies a keep, cut, or defer categorization to ensure architecture remains a minimal viable solution.

How do I eliminate over-engineering in product management?

Eliminating over-engineering in product management requires forcing a minimal viable solution by pruning project plans. You inventory constraints and edge cases, then apply cost versus value essentiality tests to cut feature bloat and output a simplified plan.