一键导入
doc-review
Review SSPs, narratives, POA&Ms, policies, and CRMs for structural completeness and quality.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Review SSPs, narratives, POA&Ms, policies, and CRMs for structural completeness and quality.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit preparation, evidence checklists, assessment simulation, gap analysis, and maturity scoring.
Draft SSP sections, SAR responses, boundary definitions, inheritance models, OSCAL guidance, and multi-framework coverage analyses.
Operational compliance workflows: continuous monitoring, calendaring, POA&M management, change management, and framework transitions.
Maps controls across cybersecurity frameworks using NIST IR 8477 Set-Theory Relationship Mapping (STRM). Use when helping with control implementation, compliance mapping, cross-framework alignment, or understanding control relationships.
Control lookup, cross-framework mapping, search, and coverage analysis across 15 compliance frameworks.
Generate tabletop exercise scenarios for incident response and contingency planning.
| name | doc-review |
| description | Review SSPs, narratives, POA&Ms, policies, and CRMs for structural completeness and quality. |
Review compliance documents for structural completeness, quality, and adherence to framework requirements. All reviews focus on structure, not security — assessing whether documents say enough, not whether described systems are secure.
| Command | Description |
|---|---|
/grc:review-ssp | Validate SSP structure, section completeness, diagrams, appendices |
/grc:review-narrative | Control narrative quality review (Five W's: What, Who, How, When, Where) |
/grc:review-poam | POA&M document review |
/grc:review-policy | Policy document review |
/grc:review-crm | Customer Responsibility Matrix review |
Use this skill when the user shares a compliance document and wants feedback on:
All document review commands MUST display this notice at the top of every response:
Before sharing GRC artifacts: Consider replacing real system names, IP addresses, personnel names, agency names, and CVE IDs with generic placeholders (e.g., "[Agency Name]", "[System Name]", "10.x.x.x"). This tool reviews structural quality — specific identifiers aren't needed for useful feedback.
grc-pro/knowledge/audits/narrative-quality-criteria.md — Five W's rubric + maturity 0-5 scalegrc-pro/knowledge/audits/document-section-requirements.md — SSP, POA&M, policy, CRM structuregrc-pro/knowledge/audits/sar-response-patterns.md — SAR response quality checklistgrc-pro/config/guardrails.md — Operational principlesWhen the grc-mcp-server is available:
| MCP Tool | Use For |
|---|---|
grc_get_oscal_control | Look up control statement text when reviewing narrative completeness |
grc_lookup_control | Get control metadata for context during reviews |
grc_search_controls | Find related controls when a narrative references multiple controls |
grc_lookup_risk | Risk context when reviewing POA&M entries |
Fallback: If MCP tools are unavailable, read knowledge files directly from grc-pro/knowledge/audits/.