compliance-officer

Maps regulatory framework controls to code artifacts and produces compliance evidence documents.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/sundarshahi/drydock --skill compliance-officer-sundarshahi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compliance-officer
Source: https://github.com/sundarshahi/drydock/tree/main/skills/compliance-officer
Command: npx skills add https://github.com/sundarshahi/drydock --skill compliance-officer-sundarshahi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Determining which regulatory frameworks apply to a product and proving that mandatory controls actually exist in code is slow, error-prone, and audit-risky when done from memory. This Skill scopes frameworks deterministically from product signals, verifies every control id live against official sources, and produces the statutory evidence auditors expect. ## Core Features & Use Cases - Deterministic Framework Scoping: Maps product signals (PHI, cardholder data, EU users, federal customers) to SOC 2, GDPR, HIPAA, PCI-DSS v4.0.1, CCPA/CPRA, ISO 27001, and FedRAMP with an auditable decision log. - Live-Verified Control Matrix: Builds per-framework control matrices where every control id, article number, and statutory clock is verified against official sources this session — never recalled from memory. - Implementation Verification & Gate: Traces each mandatory control to an implementing artifact at path:line, then renders a blocking compliance gate with remediation hand-offs or accepted-with-justification overrides. - Statutory Documents: Generates the SSP, GDPR DPIA, and a breach runbook encoding the GDPR 72-hour and HIPAA 60-day notification clocks. - Use Case: Before launching a B2B SaaS handling EU customer data, run this Skill to scope GDPR and SOC 2, verify encryption and consent controls exist in the codebase, and produce the DPIA and evidence map for the audit. ## Quick Start Ask the compliance officer to scope applicable frameworks and audit the current codebase for SOC 2 and GDPR readiness.

Frequently Asked Questions about compliance-officer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my product needs SOC 2, GDPR, or HIPAA compliance?▼

Framework scoping is determined by product signals: PHI triggers HIPAA, cardholder data triggers PCI-DSS, EU personal data triggers GDPR, California consumers trigger CCPA/CPRA, enterprise B2B sales trigger SOC 2 or ISO 27001, and US federal customers trigger FedRAMP. Each scoped framework is recorded with its evidence in a decision log.

How to verify compliance controls actually exist in code?▼

Each mandatory control is mapped to an implementing artifact at a specific path:line in the codebase, covering audit logging, encryption at rest and in transit, RBAC, retention, consent, and data residency. A control marked Met without an artifact pointer is downgraded to Missing.

What documents are needed for a GDPR or SOC 2 audit?▼

The Skill generates a System Security Plan, a GDPR Data Protection Impact Assessment when EU data is in scope, a breach runbook encoding the GDPR 72-hour and HIPAA 60-day notification clocks, and a control-evidence map linking every control to its proof artifact.

Does this Skill re-run the security audit or PII scan?▼

No. The security-engineer remains the sole authority on PII inventory and encryption audits. The compliance-officer consumes those outputs and maps them to framework controls, raising findings for the owning agent when an artifact is missing rather than implementing controls itself.

What happens when a mandatory compliance control is missing?▼

A missing mandatory control becomes a blocking finding routed into the remediation chain with an owning agent and acceptance criteria. It can only be cleared by remediating to Met or by recording an explicit accepted-with-justification override receipt with residual risk and expiry.

Can compliance control ids be trusted without live verification?▼

No. Every control id, article number, and statutory deadline must be verified live against official sources such as eur-lex, ecfr.gov, or pcisecuritystandards.org during the session. Unverified ids are tagged and may not drive a blocking gate decision.