GRC RACI diagram
Use this skill to structure the GRC content and visual pattern for responsibility assignments across GRC, security, engineering, legal, HR, procurement, vendors, and auditors. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- access review RACI
- incident response compliance RACI
- vendor review RACI
- policy lifecycle RACI
Recommended Elements
Include these when relevant:
- responsible
- accountable
- consulted
- informed roles
- controls
- cadence
- artifacts
- approvals
Recommended Output Pattern
Produce a RACI matrix, swimlane responsibility flow, or ownership map. Choose a layout that matches the audience:
- Executive: compact lifecycle/capability view with business impact labels.
- Auditor/assessor: explicit evidence, owner, control, cadence, and scope labels.
- Practitioner/engineering: operational systems, data paths, automation, failure/exception paths, and implementation detail.
draw.io Instructions
- Load and follow the
drawio skill.
- Generate native mxGraphModel XML directly. Do not generate Mermaid as the final artifact.
- Use descriptive lowercase hyphenated filenames.
- Include a legend when colors, edge styles, or containers have compliance meaning.
- Validate XML well-formedness before finalizing.
- If PNG/SVG/PDF is requested, export with embedded diagram XML when the draw.io CLI is available.
Visual Conventions
- Blue: systems, platforms, services, and automated collectors.
- Green: implemented controls, approvals, validated evidence, and compliant outcomes.
- Orange/red: risks, findings, exceptions, overdue items, gaps, and failed controls.
- Gray: manual tasks, external parties, optional steps, and out-of-scope areas.
- Dashed containers: audit scope, trust boundaries, authorization boundary, or responsibility boundary.
- Solid edges: primary process or system flow.
- Dashed edges: evidence or attestation flow.
- Dotted edges: optional, manual, exception, or escalation flow.
Quality Bar
- Make ownership explicit.
- Label regulated data, control IDs, frameworks, and evidence repositories when known.
- Show decision criteria where the process branches.
- Avoid generic boxes like "Compliance" without a role, system, artifact, or action.
- Prefer editable source of truth over screenshots.
1---2name: grc-raci-diagram3description: Use when creating a draw.io diagram for responsibility assignments across GRC, security, engineering, legal, HR, procurement, vendors, and auditors in a GRC, security, audit, compliance, privacy, cloud, or risk context.4---56# GRC RACI diagram78Use this skill to structure the GRC content and visual pattern for responsibility assignments across GRC, security, engineering, legal, HR, procurement, vendors, and auditors. Then use the `drawio` skill to generate the native editable `.drawio` file and optional PNG/SVG/PDF export.910## Common Requests1112- access review RACI13- incident response compliance RACI14- vendor review RACI15- policy lifecycle RACI1617## Recommended Elements1819Include these when relevant:2021- responsible22- accountable23- consulted24- informed roles25- controls26- cadence27- artifacts28- approvals2930## Recommended Output Pattern3132Produce a RACI matrix, swimlane responsibility flow, or ownership map. Choose a layout that matches the audience:3334- Executive: compact lifecycle/capability view with business impact labels.35- Auditor/assessor: explicit evidence, owner, control, cadence, and scope labels.36- Practitioner/engineering: operational systems, data paths, automation, failure/exception paths, and implementation detail.3738## draw.io Instructions39401. Load and follow the `drawio` skill.412. Generate native mxGraphModel XML directly. Do not generate Mermaid as the final artifact.423. Use descriptive lowercase hyphenated filenames.434. Include a legend when colors, edge styles, or containers have compliance meaning.445. Validate XML well-formedness before finalizing.456. If PNG/SVG/PDF is requested, export with embedded diagram XML when the draw.io CLI is available.4647## Visual Conventions4849- Blue: systems, platforms, services, and automated collectors.50- Green: implemented controls, approvals, validated evidence, and compliant outcomes.51- Orange/red: risks, findings, exceptions, overdue items, gaps, and failed controls.52- Gray: manual tasks, external parties, optional steps, and out-of-scope areas.53- Dashed containers: audit scope, trust boundaries, authorization boundary, or responsibility boundary.54- Solid edges: primary process or system flow.55- Dashed edges: evidence or attestation flow.56- Dotted edges: optional, manual, exception, or escalation flow.5758## Quality Bar5960- Make ownership explicit.61- Label regulated data, control IDs, frameworks, and evidence repositories when known.62- Show decision criteria where the process branches.63- Avoid generic boxes like "Compliance" without a role, system, artifact, or action.64- Prefer editable source of truth over screenshots.
grcengclub