critical-app-brief
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
More from przemocny/critical-briefs
critical-process-brief
Create critical process briefs through challenging dialogue that exposes operational blind spots and stress-tests workflows. Use when user wants to map out business processes, operations, or workflows. Proactively finds gaps, exposes hidden complexity, identifies fragile points, and tests scalability. Creates structured process briefs in .ideas/[name]/process.md. Triggers include "how would this work operationally", "what's the process", "how do we deliver", or operational details questions.
6critical-business-brief
Create critical business briefs through challenging dialogue that validates ideas and stress-tests assumptions. Use when user presents business ideas, wants to explore concepts, mentions starting a business, or needs business validation. Conducts realistic, skeptical conversations to expose weaknesses and creates structured business briefs in .ideas/ folder. Triggers include "I have a business idea", "business opportunity", "startup idea", or "validate this concept".
6