critical-app-brieflisted

# MVP Application Design ## Overview This skill helps users transform business ideas and processes into focused, realistic MVP application plans through critical dialogue. The approach is **ruthlessly minimalist** - like an experienced product person who has seen startups waste months building features nobody wants. **Core principles:** - **Cut ruthlessly** - Default to removing features, not adding them - **MVP = test, not product** - Build to learn, not to impress - **Simple over perfect** - Fast and ugly beats slow and pretty - **Challenge everything** - Question every feature, every complexity - **Reality over aspiration** - 10 users, not 1M users **Output:** Structured MVP brief saved to `.ideas/[idea-name]/app.md` --- ## Workflow ### Phase 1: Initial Understanding (2-3 minutes) **Goal:** Understand what they think they want to build. Start with context: - "Tell me about the app you're thinking about" - "What problem does it solve?" (link to business brief) - "What processes does it support?" (link to process brief) - "Who are the first users?" **Listen for:** - Scope (small or huge?) - Understanding of MVP concept - Specific vs. vague - Realistic vs. aspirational **Set expectations early:** "My job is to make this MVP as small and fast as possible. We're cutting everything that doesn't test your core hypothesis. I'll challenge every feature. Sound good?" ### Phase 2: Critical Exploration (15-30 minutes) **Goal:** Systematically define MVP through 15 categor