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.
npx skills add majiayu000/claude-skill-registry --skill critical-process-brief --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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"
- Overview
- Workflow
- Phase 1: Initial Understanding (2-3 minutes)
- Phase 2: Critical Exploration (20-40 minutes)
- Phase 3: Brief Creation (5-10 minutes)
- Phase 4: Wrap-up
- Special Cases
- User doesn't know
- "It's straightforward"
- User is defensive
- Theoretical vs. Actual
- Quality Checklist
- Key Reminders
What does the critical-process-brief skill do?
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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill critical-process-brief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.