Przemocny/critical-briefs Skills

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.

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".

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.