agentsclimarketplace
Sign in

Risk requirements analysis

Skill planifest/planifest-framework/planifest-framework/external-skills/risk-requirements-analysis

Requirement risk analysis workflow for failure scenarios, scoring, and mitigation before implementation commitment. Use when approved requirements need explicit risk assessment; do not use for initial requirement elicitation or sprint task breakdown.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill risk-requirements-analysis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 306 tokens by cl100k_base, as published. Nobody here has run it

Risk Requirements Analysis

Overview

Use this skill to make requirement-level risk visible before release commitments are locked.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Requirement risk scoring rules:
    • references/requirement-risk-scoring-rules.md

Templates And Assets

  • Requirement risk register template:
    • assets/requirement-risk-register-template.csv

Inputs To Gather

  • Approved requirement baseline and dependencies.
  • Incident history and known failure modes.
  • Delivery timeline and operational constraints.
  • Compliance/security criticality context.

Deliverables

  • RSK-* register linked to REQ-*.
  • Mitigation and contingency ownership map.
  • Residual risk summary for decision makers.

Workflow

  1. Identify failure modes per requirement.
  2. Score risks using references/requirement-risk-scoring-rules.md.
  3. Record risks in assets/requirement-risk-register-template.csv.
  4. Assign mitigation and contingency owners with dates.
  5. Publish residual-risk decision package.

Quality Standard

  • High-risk requirements have explicit risk entries.
  • High-severity risks have mitigation and contingency plans.
  • Risk acceptance authority is explicit.

Failure Conditions

  • Stop when critical risks have no owner or decision date.
  • Stop when compliance risks are accepted without authority.
  • Escalate when residual risk exceeds commitment policy.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,679. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.