compliance-drafter

Drafts SOC 2 control evidence and opens gated PRs with executive decision briefs.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill compliance-drafter-volter-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compliance-drafter
Source: https://github.com/volter-ai/open-autonomy-compiler/tree/main/profiles/soc2-baseline/skills/compliance-drafter
Command: npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill compliance-drafter-volter-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? SOC 2 controls come due on quarterly and annual cadences, and the evidence-gathering toil (pulling collaborator lists, checking policy freshness, reviewing vendor dates) falls on busy executives. This Skill performs that gathering and drafting work automatically when a soc2-control-due issue is labeled, then hands the executive a decision-ready PR to review and sign. ## Core Features & Use Cases - Control playbook execution: Identifies the due control from the issue title, looks it up in the control register, and runs the matching playbook (access-review, policy-review-ack, vendor-reassessment, risk-assessment, management-review). - Uniform evidence drafting: Produces a standardized evidence document with gathered inputs, assessment, findings, and an honest coverage/gaps section that never fabricates un-evidenced items. - Gated PR with decision brief: Commits the evidence doc and ledger artifact, re-renders the control register, and opens a PR whose body is a one-screen decision brief for the executive to edit, attest, and approve. - Use Case: A quarterly access-review control comes due. The Skill queries repository collaborators via the GitHub API, compares them against the access-control policy matrix, flags anomalies, and opens a PR the executive signs in minutes. ## Quick Start Label an issue with soc2-control-due and let the agent draft the evidence and open the review PR.

Frequently Asked Questions about compliance-drafter

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

FAQPage Schema
How do I automate SOC 2 evidence collection in GitHub?▼

Label an issue with soc2-control-due and the agent identifies the due control from the issue title, runs its playbook (e.g., querying collaborators via the GitHub API), drafts a standardized evidence document, and opens a gated PR for executive review.

What SOC 2 controls does this compliance automation cover?▼

It covers access-review (CC6.2/6.3), policy-review-ack (CC1.1/CC2.2/CC5.3), vendor-reassessment (CC9.2), risk-assessment (CC3.x), and management-review (CC4.1/4.2/CC5.1). World-act controls like pen-tests get record templates only.

Can the agent sign or approve SOC 2 controls itself?▼

No. The agent holds only code:propose permissions and never signs, approves, or marks a control done. The executive edits the assertion line, sets source to human-attested, and approves the PR as the signature.

What happens when evidence requires external data the agent cannot access?▼

The agent honestly degrades: it lists the missing input under Coverage/gaps as un-evidenced and templates the collection step. It never fabricates assessments or results for inputs like vendor SOC 2 PDFs or HR rosters.

Why does the compliance PR re-render the control register?▼

The ledger change must be reflected in compliance/control-register.md via the register render script, otherwise the soc2-register-check drift gate fails because the rendered register would not match the updated evidence ledger.