Help us improve
Share bugs, ideas, or general feedback.
From project-management
Create and maintain a project RAID log — Risks, Assumptions, Issues, Dependencies — as an Excel workbook with the right columns, severity scoring, owners, status tracking, and a roll-up view that feeds into weekly status. Use this skill any time the user wants a RAID log started, updated, audited, or rolled up, even when they say "track our risks," "we need an issues list," "log our assumptions," "what dependencies are blocking us," or "consolidate our risks for the steerco." Trigger whenever risk/issue/dependency tracking is being created or maintained so the team has one canonical source instead of five tabs in five tools.
npx claudepluginhub bpainter/composable-dxp-claude-marketplace --plugin project-managementHow this skill is triggered — by the user, by Claude, or both
Slash command
/project-management:project-management-raid-logThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A RAID log is the single canonical place for the things that could derail a project. The four columns of the acronym aren't the same kind of thing — distinguishing them is the work.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
A RAID log is the single canonical place for the things that could derail a project. The four columns of the acronym aren't the same kind of thing — distinguishing them is the work.
The skill produces a structured xlsx workbook (because most stakeholders open xlsx, and filtering/sorting matters), and explains how to maintain it across the project lifecycle.
pm-weekly-status.For the actual xlsx generation, lean on the xlsx skill — this skill defines the schema and rules; the xlsx skill handles file production.
One workbook. Four sheets, one per RAID type. Plus a Summary sheet that aggregates open items by severity.
RAID-Log-{ProjectName}.xlsx
├── Summary (read-only roll-up, formulas only)
├── Risks
├── Assumptions
├── Issues
└── Dependencies
| Column | Notes |
|---|---|
| ID | R-001, sequential. Never reuse. |
| Date raised | yyyy-mm-dd |
| Title | Short, scannable. "Contentful migration may slip Phase 2 launch." |
| Description | 1-3 sentences. What might happen and why. |
| Probability | 1 (rare) – 5 (almost certain) |
| Impact | 1 (negligible) – 5 (severe) |
| Severity | Probability × Impact (formula). Color-banded: 1-6 green, 7-14 yellow, 15-25 red. |
| Mitigation | What we're doing to reduce probability or impact. |
| Contingency | What we'll do if it happens. |
| Owner | One person. Not "the team." |
| Status | Open / Mitigating / Realized (became an Issue) / Closed (mitigated or expired) |
| Last updated | yyyy-mm-dd |
| Notes | Free text. Date-stamped entries: 2026-04-15: ... |
| Column | Notes |
|---|---|
| ID | A-001 |
| Date raised | yyyy-mm-dd |
| Assumption | The thing we're treating as true. "Client will provide content for 12 product explainers by 2026-06-01." |
| Why it matters | What plan element depends on it. |
| Validation method | How we confirm. "Confirmed in writing by client content lead." |
| Validation deadline | yyyy-mm-dd. By when we need to know. |
| Owner | One person. |
| Status | Unvalidated / Validated / Invalidated (became a Risk or Issue) / Closed |
| Last updated | yyyy-mm-dd |
| Notes | Date-stamped entries. |
| Column | Notes |
|---|---|
| ID | I-001 |
| Date raised | yyyy-mm-dd |
| Title | "Contentful API rate limit hit during initial bulk import." |
| Description | What is happening and what it's blocking. |
| Impact | 1-5 |
| Urgency | 1-5 |
| Severity | Impact × Urgency (formula). Color-banded. |
| Resolution plan | The steps being taken. |
| Owner | One person. |
| Target resolution | yyyy-mm-dd |
| Status | Open / In progress / Blocked / Resolved |
| Last updated | yyyy-mm-dd |
| Notes | Date-stamped entries. |
| Column | Notes |
|---|---|
| ID | D-001 |
| Date raised | yyyy-mm-dd |
| Dependency | "Client marketing approval on disclaimer wording." |
| Type | Internal Slalom / Client / Third-party vendor / Regulatory |
| Needed by | yyyy-mm-dd |
| Why | What it unblocks. |
| Owner (chasing) | One person on the project team. |
| Counterparty | Who owns it on the other side. |
| Status | Identified / Requested / In progress / Received / Blocked |
| Last updated | yyyy-mm-dd |
| Notes | Date-stamped entries. |
Pulls counts and tops from the four sheets:
This sheet is what gets screen-shared in steercos. Keep it free of formatting clutter.
Use 1-5 scales to keep math simple. A 5-point scale gives meaningful granularity without false precision.
Probability (Risks):
Impact (Risks & Issues):
Urgency (Issues):
The math: severity = factor1 × factor2. Range 1-25. Color bands:
Stakeholders learn this scale week over week — don't change it mid-project.
Daily: anyone can add an entry. Use Slack channel or PR template that says "raised in RAID as R-NNN."
Weekly (Thursday before status):
pm-weekly-status.Monthly / mid-phase:
The four types are not silos. Things move:
Realized — see I-NNN). Open a fresh Issue with a backlink.Backlinks are how the log stays auditable.
When asked to generate the workbook, use the xlsx skill to create the file with:
RAID-Log-{ProjectName}.xlsx (or project-appropriate name) in the workspace folderFor ongoing maintenance via this skill, accept input as either:
pm-weekly-status.pm-weekly-status (Risks & Issues table, Decisions Needed).pm-user-story.xlsx skill.pm-requirements-discovery skill.../../references/book-risk-up-front.md./80_Skills_and_Agents/consulting/references/book-essential-tools-burtonshaw.md.../../references/template-risk-up-front.md — primary deliverable for kickoff RUF