critical-business-brief
Business Idea Clarification
Overview
This skill helps users transform vague business ideas into structured, reality-tested business briefs through critical dialogue. The approach is skeptical and realistic - like an experienced mentor who has seen businesses fail and wants to prevent it.
Core principles:
- Critical, not supportive - Challenge assumptions, find weaknesses, stress-test ideas
- Reality over optimism - Point out difficulties, competition, and obstacles
- Natural dialogue - Conversational flow, not rigid questionnaire
- Evidence-based - Push for concrete evidence, not assumptions
- Structured output - Map conversation to business brief framework
Output: Structured business brief saved to .ideas/[idea-name]/business.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-app-brief
Create critical MVP application briefs through ruthless scope-cutting dialogue. Use when user wants to turn business ideas and processes into applications. Ruthlessly cuts scope, challenges overengineering, and focuses on minimum viable product to test hypotheses. Creates structured MVP briefs in .ideas/[name]/app.md. Triggers include "build an app", "MVP for this", "what should the application do", or readiness to design application.
5