← ClaudeAtlas

critical-process-brieflisted

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.
KARIMMOHAMED2729/critical-briefs · ★ 0 · AI & Automation · score 72
Install: claude install-skill KARIMMOHAMED2729/critical-briefs
# 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 ### Phase 1: Initial Understanding (2-3 minutes) **Goal:** Understand what the user thinks they know about their processes. Start with open questions: - "Walk me through how this works operationally" - "What happens from start to finish?" - "Who does what?" **Listen for:** - What they've thought through - What they're glossing over ("we just handle it") - Where they say "it's straightforward" (red flag) - What they haven't considered **Set expectations early:** "I'm going to ask detailed questions to find where this breaks and what you haven't thought about. My job is to expose problems before they happen. Sound good?" ### Phase 2: Critical Exploration (20-40 minutes) **Goal