Lists multiple specific concrete actions: identify risks, log assumptions, track issues, extract decisions from correspondence, create/update RAID log, escalate risk to issue, assess project risks, validate/challenge assumptions, capture scope-relevant decisions.

Clearly answers both 'what' (RAID log methodology with decision extraction from emails and meeting notes) and 'when' (explicit 'Use when...' clause with detailed trigger scenarios, plus a 'Trigger on:' list of specific phrases).

Excellent coverage of natural trigger terms including 'risk report', 'RAID log', 'what are the risks', 'what decisions were made', 'update the risk register', 'what assumptions are we making', 'what could go wrong', 'flag any issues', and 'extract decisions from these emails'. These are phrases users would naturally say.

Highly distinctive with a clear niche around RAID log methodology and decision extraction from correspondence. The combination of project risk management and email/meeting note analysis creates a unique, well-defined scope unlikely to conflict with other skills.

This skill is extremely verbose at ~4500+ words. It extensively explains concepts Claude already understands (what RAID logs are, why decisions matter, why assumptions fail, general project management philosophy). Large sections like 'Why most RAID logs fail,' the Sibelius project references, and lengthy explanations of risk assessment principles are educational content that Claude doesn't need. The 'silence is a risk, not an issue' section alone spans multiple paragraphs explaining a simple classification rule. Much of this reads like a training manual for a human LPM rather than concise instructions for Claude.

The skill provides detailed field structures for each RAID component (Issues, Risks, Assumptions, Decisions tables) which are concrete and actionable. The step-by-step process and decision extraction signals are specific. However, there are no executable code examples, no concrete input/output examples showing an actual email chain being processed into RAID entries, and no template showing what a completed extraction looks like. The guidance is detailed but largely descriptive rather than demonstrative.

The 4-step process (determine mode → process input → produce output → write summary) is clearly sequenced, and the risk-to-issue escalation has explicit steps. However, validation checkpoints are largely absent — there's no explicit verification step after extraction ('confirm these entries with the user before adding to the log'), no feedback loop for when the user disagrees with a classification, and no checkpoint for confirming the output matches the existing log structure when updating. The 'confirming the full picture' section is a partial validation step but it's buried deep in the document.

This is a monolithic wall of text with no bundle files and no references to external documents. Content that could easily be split — the detailed RAID methodology section, the field structure definitions, the format-specific guidance, the M365 connected mode section — is all inline. The skill references other skills (scope-change-controller, budget-and-fee-manager, etc.) but doesn't reference any supporting files for its own detailed content. At this length, the lack of any content splitting is a significant organizational failure.