
grc-diagrams
Editable draw.io diagram patterns for GRC system boundaries, evidence flows, control maps, risk treatment, audits, crosswalks, TPRM, POA&M, data flows, RACI, and operating models.
- version
- 0.1.0
- GitHub stars
- 436
Install
/plugin install grc-diagrams@grc-engineering-suiteRun it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.
Contents
Discovered from sourceSkills 13
Draw.io Diagram Skill
Generate draw.io diagrams as native .drawio files. Optionally export to PNG, SVG, or PDF with the diagram XML embedded so the exported file remains editable in draw.io.
This skill is based on the draw.io CLI workflow from jgraph/drawio-mcp/skill-cli and adapted for GRC professionals.
How to Create a Diagram
- Generate draw.io XML in mxGraphModel format for the requested diagram.
- Write the XML to a
.drawiofile in the current working directory using the Write tool. - Validate XML well-formedness before claiming the diagram is ready.
- Post-process edge routing when
npx @drawio/postprocessis already available. Skip silently if it is unavailable. Do not install it or ask the user about it. - If the user requested
png,svg, orpdf, locate the draw.io CLI, export with embedded XML, then delete the source.drawiofile after a successful export. - If the CLI is not found, keep the
.drawiofile and tell the user they can install the draw.io desktop app to enable export or open the.drawiofile directly. - Open the result when the environment supports it. If open fails, print the absolute file path.
Choosing the Output Format
Check the user's request for a format preference.
create a flowchart->flowchart.drawiopng flowchart for login->login-flow.drawio.pngsvg: ER diagram->er-diagram.drawio.svgpdf architecture overview->architecture-overview.drawio.pdf
If no format is mentioned, write the .drawio file.
| Format | Embed XML | Notes |
|---|---|---|
drawio | Native | Editable source file |
png | Yes, -e | Viewable everywhere, editable in draw.io |
svg | Yes, -e | Scalable, editable in draw.io |
pdf | Yes, -e | Printable, editable in draw.io |
jpg | No | Lossy and not editable |
Use double extensions for exported editable files: name.drawio.png, name.drawio.svg, name.drawio.pdf.
draw.io CLI Location
Try drawio on PATH first. Then use platform fallbacks:
- macOS:
/Applications/draw.io.app/Contents/MacOS/draw.io - Linux:
drawio - Windows:
C:\Program Files\draw.io\draw.io.exe - WSL2:
/mnt/c/Program Files/draw.io/draw.io.exe
Detect WSL2 with:
grep -qi microsoft /proc/version 2>/dev/null && echo WSL2
Export command:
drawio -x -f <format> -e -b 10 -o <output> <input.drawio>
WSL2 example:
"/mnt/c/Program Files/draw.io/draw.io.exe" -x -f png -e -b 10 -o diagram.drawio.png diagram.drawio
Open commands:
- macOS:
open <file> - Linux:
xdg-open <file> - WSL2:
cmd.exe /c start "" "$(wslpath -w <file>)" - Windows:
start <file>
XML Format
A .drawio file is native mxGraphModel XML. Always generate XML directly. Mermaid and CSV formats require conversion and should not be saved as native .drawio files.
Every diagram must have this structure:
<mxGraphModel adaptiveColors="auto">
<root>
<mxCell id="0"/>
<mxCell id="1" parent="0"/>
</root>
</mxGraphModel>
Cell id="0" is the root layer. Cell id="1" is the default parent layer. All diagram elements use parent="1" unless the diagram intentionally uses multiple layers.
XML Reference
For complete draw.io XML guidance, fetch and follow:
https://raw.githubusercontent.com/jgraph/drawio-mcp/main/shared/xml-reference.md
Use it for styles, edge routing, containers, layers, tags, metadata, dark mode colors, and XML well-formedness rules.
GRC Diagram Conventions
- Include control IDs, frameworks, owners, evidence repositories, systems of record, and review cadence when known.
- Use swimlanes for roles or departments: GRC, Security, Engineering, Legal, Procurement, Vendor, Auditor, Executive.
- Use containers for system boundaries, audit scope, trust zones, cloud accounts, environments, and in-scope/out-of-scope areas.
- Use dashed edges for evidence paths, dotted edges for optional or manual paths, and solid edges for process or system flows.
- Use red/orange accents for risks, findings, exceptions, overdue items, and failed controls.
- Use green/blue accents for implemented controls, automated checks, approvals, and trusted evidence.
- Include a legend when colors or edge styles have compliance meaning.
CRITICAL: XML Well-Formedness
- NEVER include ANY XML comments (
<!-- -->) in the output. - Escape special characters in attribute values:
&,<,>,". - Always use unique
idvalues for eachmxCell. - Always include root cells
id="0"andid="1". - Every edge must have a child geometry element:
<mxGeometry relative="1" as="geometry"/>. - Validate XML with a parser before finalizing.
GRC audit workflow diagram
Use this skill to structure the GRC content and visual pattern for audit planning, request lists, evidence, testing, exceptions, remediation, and reporting. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- SOC 2 audit timeline
- internal audit workflow
- external auditor request lifecycle
- control testing process
Recommended Elements
Include these when relevant:
- auditor
- GRC
- control owner
- engineering
- request list
- evidence
- testing
- exception
- remediation
- report
Recommended Output Pattern
Produce a Swimlane process map or audit timeline. 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
drawioskill. - 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.
GRC compliance operating model diagram
Use this skill to structure the GRC content and visual pattern for high-level GRC program architecture, continuous compliance operating models, three lines of defense, and executive program maps. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- continuous compliance model
- three lines of defense
- GRC platform ecosystem
- policy-control-evidence-risk-audit lifecycle
Recommended Elements
Include these when relevant:
- program capabilities
- systems of record
- governance bodies
- owners
- feedback loops
- maturity phases
- automation coverage
Recommended Output Pattern
Produce a Executive capability map, lifecycle, or GRC ecosystem diagram. 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
drawioskill. - 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.
GRC control map diagram
Use this skill to structure the GRC content and visual pattern for controls mapped across frameworks, systems, owners, risks, and evidence sources. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- SOC 2 CC6.1 to AWS IAM/Okta/GitHub
- NIST AC to ISO Annex A
- common control implementation
Recommended Elements
Include these when relevant:
- controls
- frameworks
- systems
- owners
- evidence
- risks
- inherited controls
- implementation status
Recommended Output Pattern
Produce a Hub-and-spoke control map or control coverage diagram. 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
drawioskill. - 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.
GRC regulated data flow diagram
Use this skill to structure the GRC content and visual pattern for regulated data flows, data classifications, storage, processing, transfer, access, retention, and logging. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- customer data through SaaS
- HIPAA ePHI flow
- CMMC/FedRAMP CUI flow
- PCI CHD flow
Recommended Elements
Include these when relevant:
- actors
- data classes
- systems
- stores
- flows
- boundaries
- retention
- encryption
- access
- logging
Recommended Output Pattern
Produce a Data flow diagram with trust-boundary and classification overlays. 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
drawioskill. - 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.
GRC evidence flow diagram
Use this skill to structure the GRC content and visual pattern for evidence collection, evidence lifecycle, audit evidence pipelines, and systems of record. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- AWS Config to evidence repository to auditor review
- GitHub branch protection evidence
- quarterly access review lifecycle
Control-to-evidence example
For an auditor-facing map, request the control, responsible owner, evidence artifact, review cadence and reviewer. Do not include actual evidence, credentials, sensitive paths or identifying details without authorization. If an input is unknown, label it unknown rather than inventing it. Create editable nodes and labeled relationships, not a screenshot. The fictional control-to-evidence example shows an access review; it is not a claim that a real control operates effectively.
For a simple, single control-to-evidence flow with supplied labels, the optional local generator described in the plugin README creates the editable model deterministically. Use it only when this fixed four-node pattern fits; the general workflow below remains available for other diagrams. Ask for missing fields rather than guessing, and review inputs for sensitive information. It does not scan for secrets or validate the truth of the relationships.
Validate the example from the repository root:
python3 plugins/grc-diagrams/examples/validate-control-evidence.py
The parser checks escaping, cell IDs, edge references and geometry for this specific uncompressed example; it is not a general draw.io validator or a secret scanner. Open the file in draw.io to inspect layout and editability. The example does not model exceptions, retention, or evidence access controls; adapt it to the actual engagement and review for sensitive content before sharing.
Recommended Elements
Include these when relevant:
- evidence sources
- collectors
- repositories
- reviewers
- approvers
- auditors
- retention
- freshness
- cadence
Recommended Output Pattern
Produce a Swimlane evidence lifecycle or evidence data-flow diagram. 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
drawioskill. - 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.
GRC framework crosswalk diagram
Use this skill to structure the GRC content and visual pattern for mapping controls and obligations across frameworks to show overlap, gaps, and conflicts. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- SOC 2 to ISO 27001 to NIST CSF
- FedRAMP to NIST 800-53
- CIS to SOC 2
Recommended Elements
Include these when relevant:
- source framework
- normalized control
- target framework
- one-to-one/one-to-many/partial/no-match
- gaps
- conflicts
Recommended Output Pattern
Produce a Crosswalk matrix, many-to-many map, or common-control cluster. 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
drawioskill. - 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.
GRC POA&M lifecycle diagram
Use this skill to structure the GRC content and visual pattern for POA&M items, audit findings, remediation milestones, validation, closure, and escalation paths. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- FedRAMP POA&M lifecycle
- audit finding remediation
- vulnerability exception to POA&M
- corrective action tracking
Recommended Elements
Include these when relevant:
- finding
- POA&M item
- owner
- severity
- milestone
- due date
- validation
- closure
- risk acceptance
Recommended Output Pattern
Produce a State machine, remediation workflow, or milestone timeline. 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
drawioskill. - 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.
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
drawioskill. - 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.
GRC risk treatment diagram
Use this skill to structure the GRC content and visual pattern for risk intake, scoring, treatment, exception approval, residual risk, and monitoring workflows. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- risk register lifecycle
- vulnerability-to-risk workflow
- vendor risk acceptance
- policy exception approval
Recommended Elements
Include these when relevant:
- risk source
- assessment
- inherent/residual score
- treatment choice
- owner
- approver
- due date
- monitoring
Recommended Output Pattern
Produce a Decision tree or risk treatment lifecycle. 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
drawioskill. - 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.
GRC shared responsibility diagram
Use this skill to structure the GRC content and visual pattern for cloud/SaaS shared responsibility, inherited controls, provider controls, customer controls, and evidence ownership. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- AWS/FedRAMP split
- SaaS provider/customer control split
- inherited cloud controls
Recommended Elements
Include these when relevant:
- provider
- customer
- shared
- inherited
- excluded zones
- control ownership
- evidence ownership
Recommended Output Pattern
Produce a Split responsibility, layered stack, or inherited evidence 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
drawioskill. - 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.
GRC system boundary diagram
Use this skill to structure the GRC content and visual pattern for compliance scope, authorization boundaries, trust boundaries, in-scope/out-of-scope systems, and system context diagrams. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- FedRAMP authorization boundary
- SOC 2 system boundary
- PCI CDE boundary
- HIPAA ePHI boundary
Recommended Elements
Include these when relevant:
- systems
- actors
- identity providers
- data stores
- monitoring
- boundaries
- inherited services
- exclusions
- control overlays
Recommended Output Pattern
Produce a Architecture boundary diagram, trust-zone diagram, or system context diagram. 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
drawioskill. - 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.
GRC third-party risk diagram
Use this skill to structure the GRC content and visual pattern for vendor intake, tiering, questionnaires, security/privacy/legal review, contracting, and ongoing monitoring. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- new vendor intake
- security questionnaire workflow
- vendor tiering
- DPIA handoff
- continuous vendor monitoring
Recommended Elements
Include these when relevant:
- business owner
- procurement
- legal
- privacy
- security
- vendor
- approver
- artifacts
- tiering decisions
Recommended Output Pattern
Produce a Vendor lifecycle, swimlane workflow, or tiering decision tree. 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
drawioskill. - 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.
Commands 13
Audit Workflow
Create an editable draw.io diagram for audit planning, request lists, evidence, testing, exceptions, remediation, and reporting.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-audit-workflow-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:audit-workflow SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:audit-workflow FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:audit-workflow startup SaaS, executive overview, png
Control Map
Create an editable draw.io diagram for controls mapped across frameworks, systems, owners, risks, and evidence sources.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-control-map-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:control-map SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:control-map FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:control-map startup SaaS, executive overview, png
Regulated Data Flow
Create an editable draw.io diagram for regulated data flows, data classifications, storage, processing, transfer, access, retention, and logging.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-data-flow-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:data-flow SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:data-flow FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:data-flow startup SaaS, executive overview, png
Draw.io
Create a native editable draw.io diagram from the user's request.
Arguments
$ARGUMENTS- Diagram request, context, audience, and optional output format (png,svg,pdf,jpg, or default.drawio).
Instructions
- Use the
drawioskill. - If the request is GRC-specific, also use the most relevant GRC diagram companion skill.
- Generate native mxGraphModel XML and write a
.drawiofile. - Validate XML well-formedness.
- If an export format is requested and the draw.io CLI is available, export with embedded XML for PNG/SVG/PDF.
- Return the absolute path to the created file.
Examples
/grc-diagrams:drawio flowchart for access review evidence collection
/grc-diagrams:drawio png SOC 2 system boundary for a SaaS app
/grc-diagrams:drawio svg framework crosswalk for SOC 2, ISO 27001, and NIST CSF
Evidence Flow
Create an editable draw.io diagram for evidence collection, evidence lifecycle, audit evidence pipelines, and systems of record.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-evidence-flow-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:evidence-flow SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:evidence-flow FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:evidence-flow startup SaaS, executive overview, png
Framework Crosswalk
Create an editable draw.io diagram for mapping controls and obligations across frameworks to show overlap, gaps, and conflicts.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-framework-crosswalk-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:framework-crosswalk SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:framework-crosswalk FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:framework-crosswalk startup SaaS, executive overview, png
Compliance Operating Model
Create an editable draw.io diagram for high-level GRC program architecture, continuous compliance operating models, three lines of defense, and executive program maps.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-compliance-operating-model-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:operating-model SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:operating-model FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:operating-model startup SaaS, executive overview, png
Poa&M Lifecycle
Create an editable draw.io diagram for POA&M items, audit findings, remediation milestones, validation, closure, and escalation paths.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-poam-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:poam SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:poam FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:poam startup SaaS, executive overview, png
Raci
Create an editable draw.io diagram for responsibility assignments across GRC, security, engineering, legal, HR, procurement, vendors, and auditors.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-raci-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:raci SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:raci FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:raci startup SaaS, executive overview, png
Risk Treatment
Create an editable draw.io diagram for risk intake, scoring, treatment, exception approval, residual risk, and monitoring workflows.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-risk-treatment-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:risk-treatment SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:risk-treatment FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:risk-treatment startup SaaS, executive overview, png
Shared Responsibility
Create an editable draw.io diagram for cloud/SaaS shared responsibility, inherited controls, provider controls, customer controls, and evidence ownership.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-shared-responsibility-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:shared-responsibility SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:shared-responsibility FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:shared-responsibility startup SaaS, executive overview, png
System Boundary
Create an editable draw.io diagram for compliance scope, authorization boundaries, trust boundaries, in-scope/out-of-scope systems, and system context diagrams.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-system-boundary-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:system-boundary SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:system-boundary FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:system-boundary startup SaaS, executive overview, png
Third-Party Risk
Create an editable draw.io diagram for vendor intake, tiering, questionnaires, security/privacy/legal review, contracting, and ongoing monitoring.
Arguments
$ARGUMENTS- Scope, framework(s), system(s), audience, and optional export format such aspng,svg, orpdf.
Instructions
- Use the
grc-third-party-risk-diagramskill to structure the GRC-specific content. - Use the
drawioskill to generate the native.drawiofile. - Include owners, control IDs, evidence sources, systems, risks, scope boundaries, and decision points when relevant.
- If the user requested PNG/SVG/PDF, export with embedded diagram XML when the draw.io CLI is available.
- Return the absolute path to the created file.
Examples
/grc-diagrams:third-party-risk SOC 2 access controls for AWS, Okta, and GitHub
/grc-diagrams:third-party-risk FedRAMP moderate cloud platform, auditor audience, svg
/grc-diagrams:third-party-risk startup SaaS, executive overview, png
Sponsors
Details
- Marketplace
- GRCEngClub/claude-grc-engineering
- Source
- plugins/grc-diagrams
- Category
- Workflow
More from GRCEngClub/claude-grc-engineering
All 70- grc-engineerv0.1.0
- grc-internalv0.1.0
- grc-loopv0.1.0
- grc-portfoliov0.1.0
- grc-reporterv0.1.0
- grc-tprmv0.1.0
- hitrustv0.1.0
- ind-dpdpav0.1.0
- irapv0.1.0
- ismapv0.1.0
- iso27001v0.1.0
- jp-appiv0.1.0
- nist-800-53v0.1.0
- nist-ai-600-1v0.1.0
- nist-ai-rmfv0.1.0
- nist-csf-20v0.1.0
- nydfsv0.1.0
- okta-inspectorv0.1.0
- onepassword-connectorv0.1.0
- oscalv0.1.0
- pbmmv0.1.0
- pci-dssv0.1.0
- poam-automationv0.1.0
- sg-mas-trmv0.1.0