What problem does it solve?
This Skill prevents teams and builders from rushing into code before validating the problem, user demand, scope, and critical assumptions behind an idea.
Core Features & Use Cases
- Structured Ideation: Run a focused office-hours session for startup, product, side-project, open-source, or hackathon ideas.
- Assumption Testing: Ask six forcing questions covering demand reality, current alternatives, pain specificity, the narrowest wedge, user observation, and defensibility or sustainability.
- Decision-Ready Planning: Produce an assumption challenge, biggest open question, design document, scope constraints, validation actions, and downstream handoff recommendations.
- Use Case: Use this Skill when evaluating a new SaaS concept to identify the specific user, validate the status quo, define a two-week wedge, and determine what evidence is needed before engineering begins.
Quick Start
Ask the office-hours skill to stress-test your product idea before writing any code.