Menu
Compliance program management. Propose changes, review proposals, apply approved changes, audit conformance, view change log.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Behavioral floor management. Propose changes, review proposals, apply approved changes, view status. Routes to COO as behavioral floor guardian.
Generic floor management. Routes to the declared guardian for any governance floor. Use /floor propose <floor-name> <change> to propose changes to any active floor.
Structured agent-to-agent handoff. Validates artifact, logs metrics event, dispatches receiving agent.
Run a retrospective for the last completed work item. Pulls DORA metrics, summarizes flow, captures keep/stop/start.
Interactive project setup: copy templates, configure fleet, define compliance floor, add first specialist agent.
Product Owner commands -- backlog management, prioritization, grooming, review, and status. Routes to the product-owner agent.
| name | compliance |
| description | Compliance program management. Propose changes, review proposals, apply approved changes, audit conformance, view change log. |
| argument-hint | [status|propose <change> [--domains <d1,d2>]|review <id>|apply <id>|audit|log] |
Manage the compliance program through the CRO (Chief Risk Officer). All changes to the compliance floor and targets go through this skill.
/compliance or /compliance status -- Conformance posture report/compliance propose "We MUST ALWAYS encrypt PII at rest" -- Submit a change proposal/compliance review 001 -- CRO reviews and classifies a proposal/compliance apply 001 -- CRO applies an approved change (only path through the hook)/compliance audit -- Dispatch compliance-auditor for a full check/compliance log -- View the compliance change logfloors/compliance.md (count rules), .claude/compliance/targets.md (count targets), .claude/compliance/change-log.md (recent activity), .claude/findings/register.md (compliance-related findings)..claude/compliance/proposals/..claude/compliance/proposals/<id>-<slug>.md with frontmatter (id, status: pending, type: TBD, requested-by, date) and body (change-to: floor|targets, rule before/after, rationale, benchmark reference, risk assessment). Prompt user for missing fields.--domains was provided, include domain tags in the proposal file frontmatter as domains: [d1, d2]. These are passed to the CRO as advisory triage hints.compliance-proposed event via ops/metrics-log.sh. Notify CRO of pending proposal..claude/floors/compliance/.applying with proposal ID and timestamp.floors/compliance.md or .claude/compliance/targets.md.ops/compile-floor.sh --proposal <id> — if compilation fails (exit 2), revert via git checkout -- floors/compliance.md, remove sentinel, report error. The apply is atomic..claude/floors/compliance/floor-checksum.sha256..claude/compliance/change-log.md.compliance-applied event. Update proposal to "applied"..claude/compliance/change-log.md.| Subcommand | Model | Rationale |
|---|---|---|
/compliance status | Sonnet | Data aggregation |
/compliance propose | Sonnet | Structured formatting |
/compliance review | Opus | Judgment: risk classification, Cx consultation |
/compliance apply | Sonnet | Controlled file modification |
/compliance audit | Sonnet | Dispatches Sonnet-tier auditor |
/compliance log | Sonnet | Data lookup |
Implementers can override to add domain-specific proposal templates, automated compliance scanning (SAST/DAST), or integration with external GRC tools.