requirements-risk-assessment

Identify and prioritize requirements engineering risks using condition-consequence statements and exposure scoring.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-risk-assessment-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-risk-assessment
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/requirements-risk-assessment
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-risk-assessment-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Requirements defects are the largest source of project failures, costing 50-200x more to fix after deployment. This Skill makes risks from elicitation gaps, ambiguous specifications, unstable requirements, and weak change control visible and manageable before they become costly downstream defects. ## Core Features & Use Cases - Condition-Consequence Risk Statements: Write precise IF-THEN risk statements that name specific stakeholders, requirements, and consequences instead of vague worries. - Risk Exposure Prioritization: Score each risk with probability x impact (1-9 scale) so the team focuses mitigation effort on risks scoring 6 or above. - RE-Specific Risk Categories: Systematically cover elicitation, analysis, specification, validation, and management risks with guided brainstorming prompts, a fill-in template, and a worked ChemTrack example register. - Use Case: A business analyst whose last project failed due to missed regulatory requirements builds a living risk register with owners, deadlines, and milestone-based reviews to prevent recurrence. ## Quick Start Ask the agent to run a requirements risk assessment for your project and produce a risk register with condition-consequence statements, exposure scores, and mitigation owners.

Frequently Asked Questions about requirements-risk-assessment

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

FAQPage Schema
How do I identify risks in requirements engineering?▼

Brainstorm risks across five RE categories: elicitation, analysis, specification, validation, and management. Use prompts like which stakeholders were not interviewed, which requirements contain TBD placeholders, and whether a baseline and change control exist.

What is a condition-consequence risk statement?▼

A condition-consequence statement uses the format IF [specific condition] THEN [specific consequence]. It forces precision by naming actual stakeholders, requirement IDs, and project impacts instead of vague statements like requirements might be incomplete.

How do I prioritize requirements risks?▼

Calculate risk exposure as probability times impact, each rated 1-3, giving scores from 1 to 9. Risks scoring 6 or above demand immediate mitigation with an assigned owner and deadline.

When should a requirements risk register be updated?▼

Review the register at every project milestone, sprint review, or phase gate. Update probability and impact ratings, add new risks from ongoing elicitation, and escalate any risk whose exposure has increased.

What are common mistakes in requirements risk assessment?▼

Common pitfalls include vague risk statements, treating the register as a one-time document, rating all risks as high, and defining mitigations without named owners. Each mitigation needs a specific person and deadline.