Risk Review Process
Project Manager Official v1.1.27Identifies risks, scores them, and produces a register update
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 6 nodes
Risk Review Process
Identifies risks, scores them, and produces a register update
Risk Register Entry
Formatting each scored risk into a formal, structured register entry with owner, mitigation actions, and contingency plan
Assess Risk
Core prompt for identifying and scoring project risks
Risk Register Entry
Creates a structured risk register entry
RAID Log Template
Template for Risks, Assumptions, Issues, Dependencies tracking
Risk Heatmap Template
5x5 probability-impact risk visualization grid
Requirements 1 service
- LLM Service
Security Passed
Detected
- Services: llm-service
- Permissions:
- Data Handling:
Version history 17 releases
GH#863 (Wave 2) — wire the never-invoked `risk-register-entry` so the register is actually produced. The bundle shipped a `risk-register-entry` prompt ("Creates a structured risk register entry") and the docs described a register-creation stage, but the `execution:` block only ran `assess-risk → language-polish` — so the pipeline output a polished risk *assessment*, not the risk *register* that is the deliverable of a risk-review process (K-045 intent/output mismatch). Restored the intended graph: inserted a **Risk Register Entry** step (backed by the new `risk-register-builder` skill so it is `from_step`-addressable) between the assessment and the polish, ordered `assess-risk → risk-register-entry → language-polish`, and converted the register prompt's positional `{{steps.Risk Assessment.output}}` ref to an explicit `from_step` binding (`{{step.context.risk_assessment}}` ← Assess Risk). Also completed the tail: repinned `polish-language` 1.0.1→1.0.6 (the version exposing the bindable `source` slot) and bound `language-polish`'s `source` ← the Risk Register Entry, so the `output_step` polishes the register rather than its positional previous — correct end-to-end. No new required inputs.
GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.
GH#745 — declare per-step `output: {name, type}` on every execution step (risk_assessment/text, polished_review/text). Lights up the #744 rich flow-map. Content-only; no bindings or logic changes.
GH#645 Row 3b — migrate to K-037 dep-referenced schema. Strip 7 inline shared-content files and declare 7 hub-shared deps (UUID id + slug name + version + checksum from `gen-dep-checksums.mjs`). Closes pre-Step-3 inline-vendoring for this bundle.
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Project Manager
View all →Roadmap Update Flow
Revises roadmap based on velocity trends and priority changes
Sprint Summary Pipeline
Pulls sprint tickets from Linear via MCP, analyzes velocity and status, and generates a stakeholder-ready sprint report
Sprint Planning Pipeline
End-to-end sprint planning from backlog to committed plan