Skip to content

mattgierhart/PRD-driven-context-engineering / .claude/skills/prd-v05-risk-discovery-interview

prd-v05-risk-discovery-interview

Verified

Surface risks through guided questioning, helping users consider pivots, constraints, and prioritization during PRD v0.5 Red Team Review. Triggers on requests to identify risks, stress-test the idea, perform red team review, or when user asks "what could go wrong?", "identify risks", "red team", "risk assessment", "challenge assumptions", "stress test the idea". Consumes all prior IDs (CFD-, BR-, FEA-, PER-, UJ-, SCR-) as interview context. Outputs RISK- entries with owner decisions and mitigations. Feeds v0.5 Technical Stack Selection.

FileKindSize
SKILL.mdskill md13.1 KB
assets/risk.mdmarkdown3.8 KB
references/examples.mdmarkdown4.8 KB
references/question-bank.mdmarkdown3.7 KB

references/question-bank.md

View on GitHub
# Risk Discovery Question Bank

## Opening Questions

Use these to frame the interview:

- "Let's stress-test your plan. I'll ask challenging questions—the goal is to find risks we can mitigate, not to kill the idea."
- "Imagine it's 6 months from now and the product failed. What's the most likely reason?"
- "What's the thing you're most worried about that you haven't told anyone?"

---

## Market Risk Questions

**Competition:**
- "What happens if [competitor] launches this feature in the next 60 days?"
- "What would a well-funded competitor do to block you?"
- "Why hasn't [incumbent] already built this?"

**Demand:**
- "What evidence do you have that users will pay for this?"
- "How confident are you in your market size estimate?"
- "What would cause the market to shrink?"

**Timing:**
- "Is there a market window closing? When?"
- "What macro trend could invalidate your thesis?"
- "Are you too early or too late? How do you know?"

---

## Technical Risk Questions

**Complexity:**
- "Which feature has the most technical uncertainty?"
- "What have you never built before?"
- "What could take 10x longer than you expect?"

**Dependencies:**
- "What external API or service could break your product?"
- "What happens if [critical dependency] changes its API?"
- "What integration is most complex?"

**Performance:**
- "What happens at 10x your expected load?"
- "Where could latency become a problem?"
- "What data growth could break your architecture?"

**Security:**
- "What data are you storing that would be bad if leaked?"
- "What compliance requirements apply?"
- "What would a security researcher find in your code?"

---

## Adoption Risk Questions

**Onboarding:**
- "What's the biggest friction point in [UJ-001]?"
- "How long does it take to reach the 'aha moment'?"
- "What could cause a user to give up during setup?"

**Behavior Change:**
- "What behavior change are you asking users to make?"
- "What habit must users break to adopt this?"
- "How long until users see value?"

**Retention:**
- "What would cause a user to churn in week 1?"
- "What competitor feature could pull users away?"
- "What's your plan if activation rate is 50% of target?"

---

## Resource Risk Questions

**Scope:**
- "If you had to cut scope by 50%, what stays?"
- "What's the minimum viable version of this?"
- "Which feature would you cut if it took 3x longer than expected?"

**Team:**
- "What skill does the team lack?"
- "What happens if a key team member leaves?"
- "Do you have the right expertise for [complex feature]?"

**Budget:**
- "How long is your runway for validation?"
- "What's your burn rate during development?"
- "What happens if you can't raise the next round?"

---

## Dependency Risk Questions

**External Services:**
- "What external service could block your launch?"
- "What's your fallback if [critical API] is unavailable?"
- "What happens if [vendor] changes pricing by 10x?"

**Partners:**
- "What partner relationship is critical?"
- "What happens if [partner] says no?"
- "Who else must cooperate for this to work?"

**Regulatory:**
- "What regulatory requirement could block launch?"
- "What compliance certifications do you need?"
- "What legal review is required?"

---

## Timing Risk Questions

**Deadlines:**
- "Is there a hard deadline? What happens if you miss it?"
- "What external event affects your timeline?"
- "What's driving the launch date?"

**Seasonality:**
- "Is there seasonality in your market?"
- "When is the worst time to launch?"
- "What market event could accelerate or delay you?"

---

## Follow-Up Questions

Use these to dig deeper:

- "What makes you say that?"
- "What would change your mind?"
- "What evidence would prove you wrong?"
- "Who disagrees with you on this?"
- "What's the worst-case scenario?"
- "How would you know if this risk is materializing?"
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall