Risk Identification · Pattern Prediction · Engine Renderer

Your AI Risk Specialist

Drop your project brief in. Get a fully scored, prioritized risk register — grounded in specific project facts — in seconds. Built for Claude Projects. No setup beyond drag-and-drop.

Get RIPPER on GitHub → See the output ↓

Project Risk Register — Top 5 Risks

MKR Motor Controller Development — KreegCo · June 2026

Critical: 4 High: 1 5 shown · 15 total

ID	Risk	Cat.	P	I	Score	Priority
R01	Hard deadline, no float	Schedule	4	5	20	Critical
R02	Engineering lead: sole designer	Resource	4	5	20	Critical
R03	Components unordered; 26-wk lead	External	4	5	20	Critical
R04	FCC cert timeline uncontrolled	External	4	4	16	Critical
R05	Customer qual driven by customers	External	3	4	12	High

Process

How RIPPER works

Five steps from project brief to actionable risk register. No prompting required — just ask.

Load project context

Drop the RIPPER folder into a Claude Project. The project brief, scoring rules, and identification patterns load automatically — no copy-pasting required.

Identify risks

RIPPER scans the project brief against 12 identification patterns across 6 risk categories: schedule, budget, scope, resource, technical, and external.

Score each risk

Every risk is scored on Probability (1–5) × Impact (1–5), with rationale grounded in specific project facts — not generic boilerplate.

Generate the register

A structured HTML risk register is produced — sorted critical first, with detail cards, mitigation recommendations, and contingency plans for every risk.

Refine interactively

Challenge a score, add a risk RIPPER missed, mark one as mitigated, or ask what-if questions. RIPPER updates the register through conversation.

Risk Scoring Matrix — Probability × Impact

Probability

Impact

Low (1–3)

Medium (4–7)

High (8–14)

Critical (15–25)

Capabilities

Built to make decisions, not ask for them

Every design choice removes friction. RIPPER acts on clear intent — no hand-holding, no clarifying questions before it produces output.

🔍

Pattern-Based Identification

12 identification patterns detect risk across 6 categories. Each pattern maps to a score range, then calibrates against project-specific signals.

📊

Scored & Prioritized

Every risk gets a Probability × Impact score (1–25) with four priority tiers. The register sorts critical-first automatically.

💬

Interactive Refinement

Challenge a score, add a missed risk, mark one mitigated, or run what-if scenarios. The register updates in real time through conversation.

📄

HTML Output, Zero Dependencies

The register is a self-contained HTML file with inline styles. No external stylesheets, no frameworks. Open it in any browser and it works.

Coverage

Six categories. One specialist.

RIPPER identifies risks across every dimension of a project — not just the obvious schedule and budget concerns.

📅

Schedule

Hard deadlines, compressed timelines, sequential external dependencies, and milestones with no float or buffer.

💰

Budget

Thin contingency reserves, cost exposure from scope or timeline changes, and underfunded phases of work.

📐

Scope

Technically undefined deliverables, stakeholder misalignment, and elements with no agreed implementation approach.

👤

Resource

Single points of failure on people, shared resources across projects, and key-person dependencies with no backup.

⚙️

Technical

New technology adoption, legacy system integrations, undefined implementation approaches, and unknown complexity.

🌎

External

Regulatory approvals, vendor performance, customer-controlled processes, and events outside the project team’s control.

Output

This is what you get

A self-contained HTML risk register ready for a project kickoff or status report — no reformatting required.

risk-register.html

Project Risk Register — Top 5 Risks

Project	MKR Motor Controller Development and SBR Migration — KreegCo
Analysis date	June 2026
Input source	reference/Project-files/demo-project.md
Scope	Five highest-scoring risks · Full register contains 15 identified risks

Critical: 4 High: 1 5 risks shown

Risk Summary

ID	Risk Description	Category	P	I	Score	Priority	Status
R01	8-month hard deadline with no float	Schedule	4	5	20	Critical	Open
R02	Engineering lead: sole designer, no dedicated capacity	Resource	4	5	20	Critical	Open
R03	Key components not ordered; 26-week lead time on WSP4953	External	4	5	20	Critical	Open
R04	FCC certification timeline outside KreegCo control	External	4	4	16	Critical	Open
R05	Customer qualification timelines driven by customers, not KreegCo	External	3	4	12	High	Open

Risk Details

Critical — Score 20 R01 — 8-month hard deadline with no float

Description: The 8-month deadline is fixed by physical SBR component inventory exhaustion. When inventory is gone, production stops regardless of MKR readiness. This is a physical constraint, not a business preference. There is no float on this deadline.
Category: Schedule
Probability: 4 (Likely) — Multiple sequential external dependencies — FCC certification, four separate customer qualifications — each of which could individually cause a slip. Cascading delays are more likely than not over an 8-month window.
Impact: 5 (Critical) — If MKR is not production-ready before SBR inventory is exhausted, KreegCo cannot fulfill orders for any of the four OEM customers, triggering contract penalties and supply disruption.
Mitigation: Build a full project schedule mapping all milestones against the Month 10 constraint. Target Month 9 as the internal completion gate. Identify the critical path now.
Contingency: If a slip becomes likely, prioritize customers with shortest qualification lead times (Customer C — 2–3 weeks) for earliest cutover.
Owner: Director of Sales and Operations
Status: Open

Critical — Score 20 R02 — Engineering lead is sole designer with no dedicated capacity

Description: The Director of Engineering is the sole hardware and firmware designer while simultaneously owning production support, warranty escalations, and two other active development projects.
Category: Resource
Probability: 4 (Likely) — Four concurrent responsibilities over a 10-month timeline makes capacity conflicts highly probable. Any production escalation will compete directly with MKR milestone work.
Impact: 5 (Critical) — Hardware design, PCB layout, and firmware development cannot proceed without this individual. Delay cascades to every downstream milestone including FCC testing and customer samples.
Mitigation: Formally allocate a defined percentage of this individual’s capacity to MKR. Identify contract engineering options before one is needed under timeline pressure.
Owner: Owner (project sponsor)
Status: Open

Conversations

Refine through conversation

The register isn’t static. Ask follow-up questions, challenge scores, and update status — RIPPER responds and reflects every change.

You

“What are the top 5 risks for this project?”

RIPPER

The five highest-scored risks for the MKR project are:

R01 — 8-month hard deadline, no float | Schedule | Score: 20 (Critical)
The deadline is physical — SBR inventory exhaustion, not a business preference. Multiple sequential external dependencies make a slip likely without active management.

R02 — Engineering lead: sole designer | Resource | Score: 20 (Critical)
Single point of failure across hardware and firmware with four concurrent responsibilities over the project window…

You

“Rescore R04 — probability 3, impact 4. We’ve already engaged the test lab.”

RIPPER

R04 updated.

FCC Certification Timeline — previous score: 16 (Critical, P4 × I4).
New score: 12 (High, P3 × I4). Manual adjustment — test lab engagement reduces submission lead time risk, lowering probability from Likely to Possible.

R04 moves from Critical to High. Register reordered. R05 is now the fifth-ranked risk at Score 12.

Ready to manage risk like a specialist?

Drop it into a Claude Project. Ask a question. Get a register.

Get RIPPER on GitHub → What’s coming next — planned PM agent modules

Module 2 — Coming Soon

Schedule Analyst

Critical path identification, milestone tracking, and timeline variance analysis.

Module 3 — Coming Soon

Budget Tracker

Cost variance monitoring, contingency burn rate, and budget exposure forecasting.

Module 4 — Coming Soon

Scope Evaluator

Change request analysis, scope creep detection, and impact assessment.

Module 5 — Coming Soon

Comms Drafter

Stakeholder update drafting, escalation notices, and status report generation.