From quorum
Analyzes requirements for failure modes in external dependencies, data persistence, user input, and infrastructure. Classifies severity, defines mitigations/recovery, generates mandatory Work Breakdown items for high-severity risks.
npx claudepluginhub berrzebb/quorum --plugin quorumSystematically analyze what can go wrong with each requirement before implementation begins. HIGH severity failures become mandatory Work Breakdown items — catching them before code prevents costly rework. - After DRM confirmation, before Work Breakdown drafting - When adding new P0/P1 requirements to an existing track - When audit findings reveal unhandled failure modes 1. **PRD** with priorit...
Fills Nyquist validation gaps by generating runnable behavioral tests for phase requirements, running them adversarially, debugging failures (max 3 iterations), verifying coverage, and escalating blockers.
Share bugs, ideas, or general feedback.
Systematically analyze what can go wrong with each requirement before implementation begins. HIGH severity failures become mandatory Work Breakdown items — catching them before code prevents costly rework.
quorum tool blast_radius and quorum tool dependency_graph (optional)For each selected FR, generate failure scenarios across 4 categories:
| Category | Example Scenarios |
|---|---|
| External Dependencies | API timeout, rate limiting, auth token expiry, service degradation, version mismatch |
| Data & Persistence | Duplicate records, race conditions, schema migration failure, data corruption, constraint violation |
| User Input | Invalid format, injection attacks, size limits exceeded, encoding issues, concurrent edits |
| Infrastructure | Network partition, disk full, memory exhaustion, container restart, clock skew |
Not every category applies to every FR — skip categories that are genuinely impossible.
| Severity | Criteria | Action |
|---|---|---|
| HIGH | Data loss, security breach, system unavailable, corruption | Mandatory new WB |
| MEDIUM | Degraded experience, partial failure, recovery possible | New WB unless explicitly deferred |
| LOW | Cosmetic, logged warning, self-healing | Note in existing WB as detail |
For each HIGH/MEDIUM failure, define:
## FR-{N}: {Title}
| Scenario | Category | Severity | Impact | Mitigation | New WB? |
|----------|----------|----------|--------|------------|---------|
| API timeout on payment | External | HIGH | Transaction lost | Retry + idempotency key | ✓ WB-{N} |
| Duplicate submission | Data | MEDIUM | Double charge | DB unique constraint | ✓ WB-{N} |
| Invalid currency code | Input | LOW | 400 error | Validation in handler | — |
Collect all new WBs generated from failure analysis. In interactive mode, present and wait for confirmation. In headless mode, auto-generate for external dependencies and data persistence — mark assumptions as [FDE-ASSUMPTION].