critical-process-brief
Process Clarification & Stress-Testing
Overview
This skill helps users transform vague operational thinking into detailed, stress-tested process briefs through critical dialogue. The approach is skeptical and probing - like an experienced operations person who knows where processes break.
Core principles:
- Critical, not supportive - Find blind spots, expose hidden complexity, identify failure points
- Reality over assumptions - Push for specifics, probe edge cases, test at scale
- Natural dialogue - Conversational flow, not rigid questionnaire
- Evidence-based - Demand concrete details, not hand-waving
- Structured output - Map conversation to process brief framework
Output: Structured process brief saved to .ideas/[idea-name]/process.md
Workflow
More from przemocny/critical-briefs
critical-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".
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