Raid Log
Create and maintain a RAID log — Risks, Assumptions, Issues, and Dependencies — for a project or program. Use when the user says "RAID log", "risk register", "track our risks/assumptions/issues/dependencies", "log a new risk", or needs a structured way to track and review threats and open items.
Install
$ agentstack add skill-janellecipriano-pm-skills-raid-log ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-janellecipriano-pm-skills-raid-log) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
RAID Log
Build and maintain a RAID log: the running record of Risks, Assumptions, Issues, and Dependencies that could affect delivery.
Definitions (keep them distinct)
- Risk — something that might happen and would have impact. Has probability + impact + mitigation.
- Assumption — something taken as true without proof; becomes a risk if wrong. Track validation.
- Issue — a risk that has materialized, or a current problem. Needs an owner and resolution.
- Dependency — something you need from (or owe to) another team/vendor, with a date.
When to use
- Standing up risk tracking for a project, or adding/updating entries during delivery.
- Prepping a risk review or steering-committee section.
Process
- Classify each item into exactly one of R / A / I / D.
- For risks: score Probability (H/M/L) and Impact (H/M/L), derive severity, and give a mitigation + owner. Note a trigger/early warning if useful.
- For assumptions: note how/when it will be validated and the impact if false.
- For issues: capture impact, owner, target resolution date, and status.
- For dependencies: capture what, direction (we need / they need), owner on both sides, and needed-by date.
- Give every entry a stable ID, an owner, a status (Open/Mitigating/Closed), and a last-updated date. Sort by severity.
Output format
Use [templates/raid-template.md](templates/raid-template.md). When updating an existing log, preserve IDs and show what changed.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: janellecipriano
- Source: janellecipriano/pm-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.