risks

This pipeline requires a protocol directory with at least a real problem statement — if that's missing, say so and route through Claudity's start skill (problem clarification) first. If the brainstorming mailbox already has pending items, offer failure-analysis instead (the status script's Process Availability section shows which phase is recommended). If the user named a focus area when invoking this skill, honor it; follow the guide below from the beginning.

Failure Brainstorming

This process generates raw failure modes through direct analysis, specialist thinker subagents, and human contributions. Raw failures accumulate in a pool until they're ready for analysis and grouping.

Overview

The goal of failure brainstorming is breadth: come up with as many things as possible that could go wrong. This is the creative, divergent phase — don't filter, don't group, don't worry about duplicates. That's what failure analysis is for.

Brainstorming can happen over time. Multiple runs can contribute, humans can add their own insights, and the pool grows until someone decides it's ready for analysis. This process can be run multiple times, each run adding to the same pool.

Tools Available

You have MCP tools (from the clarity-agent server) for recording your findings. Always use these — do not write files directly. The tools own placement, naming, and format; hand-written files end up in the wrong location and are invisible to the pipeline.

record_failure

Record a failure mode to the brainstorming mailbox: call the record_failure tool with title ("Short title of what goes wrong") and description ("1-3 sentences: what fails, how, who is harmed").