Micro-SaaS Scoper

Overview

This skill decides whether a wedge should become software now, later, or not at all. The goal is to protect against premature product building and to force a narrow MVP when software is justified.

Load references/productization-signals.md when deciding readiness. Load references/mvp-boundaries.md when narrowing the scope.

When to use

• When a service or workflow may be ready to productize
• When a user wants a micro-SaaS and needs the product wedge defined
• When there is tension between manual delivery and automation

Do NOT use when: