prd-v05-risk-discovery-interview

Identify and structure project risks through a guided PRD risk discovery interview.

193|9|Updated Jul 10, 2025
One-click install
npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v05-risk-discovery-interview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-v05-risk-discovery-interview
Source: https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v05-risk-discovery-interview
Command: npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v05-risk-discovery-interview

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Teams often miss critical risks in early product definitions, leading to scope drift and unexpected pivots during delivery. This Skill provides a guided interview framework to surface risks early and structure them into a formal risk register.

Core Features & Use Cases

  • Guided interview prompts across Market, Technical, Adoption, Resource, Dependency, and Timing categories.
  • Automatic generation of RISK- entries with owner decisions, mitigations, and review timelines.
  • Consumes prior IDs (CFD-, BR-, FEA-, PER-, UJ-, SCR-) as context to maintain traceability during PRD reviews and Red Team sessions.
  • Feeds risk signals into downstream decisions such as the v0.5 Technical Stack Selection.

Quick Start

Run the guided risk interview with the user, collecting risk inputs and generating structured RISK- entries.

Frequently Asked Questions about prd-v05-risk-discovery-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a guided risk discovery interview for PRD reviews?

A guided risk discovery interview is a structured framework to surface project risks early. It prompts stakeholders across Market, Technical, Adoption, Resource, Dependency, and Timing categories to prevent scope drift during product delivery.

How do I identify and structure project risks during a PRD review?

Identify project risks by running a guided interview that captures inputs across six risk categories. The session structures findings into formal RISK- entries with assigned owners, mitigation strategies, and review timelines.

How does risk discovery consume prior PRD context like features and user journeys?

Risk discovery consumes prior context by ingesting existing IDs such as CFD-, BR-, FEA-, PER-, UJ-, and SCR-. This maintains traceability during PRD reviews and Red Team sessions to ensure comprehensive risk coverage.

Can I use this risk interview framework for Red Team sessions?

Yes, you can use this guided risk interview for Red Team sessions. It surfaces discovery questions across six risk categories and generates structured RISK- entries to formally capture adversarial findings and mitigation strategies.

What's the best way to document risk mitigation decisions for stakeholders?

The best way to document risk decisions is generating structured RISK- entries. Each entry captures the specific risk, owner decisions, mitigation actions, and review timelines to maintain accountability across stakeholders.

What downstream processes rely on the outputs of a PRD risk discovery interview?

The RISK- entries generated by the risk discovery interview feed directly into downstream decisions such as v0.5 Technical Stack Selection. This ensures identified technical and resource risks inform architectural choices.