What it does

This skill bridges the gap between a raw idea and technical implementation by generating a comprehensive business logic document. It forces clarity on the "why" and "who" before a single line of code is written or a UI is designed. It takes a product concept, client brief, or research data and transforms it into a structured business-model.md file that serves as the strategic North Star for the entire development lifecycle.

How it works

The skill follows a rigorous 11-step process to define the product in plain English, identify the core problem/solution fit, and establish a monetization hypothesis. It doesn't just list features; it identifies the buyer vs. the user, maps out user objections, and defines specific go-to-market channels. It integrates seamlessly with downstream dev tasks like design docs, UX flows, and implementation planning.

Why use this skill

Unlike standard AI prompting, which often results in generic startup jargon, this skill is programmed with strict "anti-patterns." It intentionally avoids scope creep, separates buyer motivations from user needs, and demands specific success metrics. By defining strategic "non-goals," it prevents wasted engineering hours on features that don't align with the business objective. It ensures that every technical decision made later has a clear business justification.