Skip to content

secondsky/claude-skills / plugins/plan-interview/skills/plan-interview

plan-interview

Verified

Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.

references/phase-4-risks.md

View on GitHub
# Phase 4: Risks & Tradeoffs - Deep Dive

Extended guidance for surfacing, assessing, and mitigating risks.

---

## Risk Categorization Questions

**Technical Risks**:
- "What technical unknowns could derail us?"
- "What parts of the implementation are we least confident about?"
- "What dependencies are most likely to cause problems?"

**Business Risks**:
- "What if users don't want this feature?"
- "What if the market changes while we're building?"
- "What competitive risks are we facing?"

**Operational Risks**:
- "Can we maintain this long-term with our team?"
- "What happens when key people leave?"
- "Do we have the operational capacity for this?"

**Security Risks**:
- "What's the worst-case security breach?"
- "What data could be exposed or corrupted?"
- "What would attackers target?"

**Timeline Risks**:
- "What could cause us to miss the deadline?"
- "What dependencies have we underestimated?"
- "What scope could creep?"

---

## Impact/Probability Assessment

**Impact Assessment**:
- "If this risk materializes, what's the damage?"
- "Is it recoverable or catastrophic?"
- "Who is affected? How many people?"

**Probability Assessment**:
- "How likely is this to happen? (1-10 scale)"
- "What would increase/decrease the probability?"
- "Have we seen this happen before in similar projects?"

**Prioritization Matrix**:
| Impact | High Probability | Low Probability |
|--------|------------------|-----------------|
| **High** | Critical - Must mitigate | Important - Have a plan |
| **Low** | Monitor - Watch closely | Accept - Document only |

**Risk Questions by Priority**:
- "What are our top 3 critical risks?"
- "What are we choosing to accept? Why?"
- "What's our risk appetite for this project?"

---

## Blast Radius Analysis Questions

**Failure Containment**:
- "If this component fails, what else breaks?"
- "Can failures be isolated?"
- "What's the blast radius of a worst-case failure?"

**Cascade Scenarios**:
- "Walk me through a cascade failure scenario."
- "What's the domino effect if [critical component] fails?"
- "How do we prevent cascades?"

**Recovery Time**:
- "How long to recover from a failure?"
- "What's the recovery process?"
- "Who needs to be involved in recovery?"

---

## Reversibility Assessment Questions

**One-Way Doors**:
- "What decisions are irreversible?"
- "What data migrations can't be undone?"
- "What contracts are we locked into?"

**Two-Way Doors**:
- "What decisions can we easily reverse?"
- "What's the cost of reversing each decision?"
- "How long does reversal take?"

**Decision Timing**:
- "When must we commit to irreversible decisions?"
- "Can we defer any one-way decisions?"
- "What information would change our decision?"

---

## Monitoring Triggers Questions

**Early Warning Signs**:
- "What signals indicate a risk is materializing?"
- "What metrics should we watch?"
- "How early can we detect problems?"

**Thresholds & Alerts**:
- "At what threshold do we take action?"
- "Who gets alerted when thresholds are crossed?"
- "What's the response time expectation?"

**Escalation Path**:
- "When do we escalate to leadership?"
- "What decisions can the team make autonomously?"
- "What requires executive approval?"

---

## Contingency Planning Questions

**Plan B Development**:
- "For each critical risk, what's Plan B?"
- "How quickly can we switch to Plan B?"
- "What's the cost of switching?"

**Decision Authority**:
- "Who makes the call to activate Plan B?"
- "What information triggers the decision?"
- "What's pre-approved vs needs approval?"

**Resource Allocation**:
- "Do we have resources reserved for contingencies?"
- "What can we deprioritize to address emergencies?"
- "What's the contingency budget (time, money, people)?"

---

## Known Tradeoffs Questions

**Conscious Compromises**:
- "What are we deliberately choosing NOT to do?"
- "Why is this tradeoff acceptable?"
- "What would change our minds?"

**Tradeoff Documentation**:
- "Who is aware of and has accepted this tradeoff?"
- "Is this documented somewhere?"
- "What's the plan to revisit this decision?"

**Tradeoff Implications**:
- "What are the downstream effects of this tradeoff?"
- "Who is negatively affected? Do they know?"
- "What's the long-term cost?"

---

## Risk Register Template

```markdown
## Risk: [Name]

**Category**: Technical / Business / Operational / Security / Timeline

**Description**: [What could go wrong]

**Probability**: High / Medium / Low
**Impact**: High / Medium / Low
**Priority**: Critical / Important / Monitor / Accept

**Trigger Signs**: [Early warning signals]

**Mitigation Plan**: [How we prevent or reduce this risk]

**Contingency Plan**: [What we do if it happens]

**Owner**: [Who is responsible]

**Last Reviewed**: [Date]
```

---

## Tradeoff Documentation Template

```markdown
## Tradeoff: [Name]

**Decision**: [What we decided]

**Alternatives Considered**:
1. [Alternative A] - Rejected because [reason]
2. [Alternative B] - Rejected because [reason]

**Why This Choice**: [Rationale for the decision]

**Accepted Downsides**:
- [Downside 1]
- [Downside 2]

**Conditions for Revisiting**: [When we would reconsider]

**Stakeholders Consulted**: [Who agreed to this]

**Date**: [When decided]
```

---

## Red Flags to Watch For

- **No identified risks**: Every project has risks
- **All low probability**: Optimism bias
- **No mitigation plans**: "We'll deal with it if it happens"
- **Single point of failure**: One person, one system, one vendor
- **Undocumented tradeoffs**: Decisions made but not recorded
- **No contingency plans**: "What's Plan B?" "We don't need one"

When you encounter these, probe deeper and insist on realistic risk assessment.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 197kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 197kUpdated Claude CodeCodexVerifiedInstall