compliance-policy
Regulatory and change-management obligations as constraints on specs, plans, releases and reviews.
Skill by bibutikoley
Chalk Labs
Need help deploying compliance-policy?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/bibutikoley-compliance-policy
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: security, writing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/compliance-policy
What's inside
- Skill name
compliance-policy- Description
- Regulatory and change-management obligations as constraints on specs, plans, releases and reviews. Use when writing spec.md or plan.md, when a change affects regulated processes, audit trails, records retention, customer communications, or when preparing a release, and during the Compliance review pass.
- License
- MIT
- Instructions
- 32 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
<!-- TEMPLATE. Replace <...> with your regime (e.g. SOX, PCI DSS, HIPAA, GDPR, FCA/SEC rules, ISO 27001) and internal change policy.
Source of truth: <link to compliance manual / change management policy> Owner: <compliance lead> Last reviewed: <YYYY-MM-DD> -->
# Compliance and change-management policy
## Traceability (always)
- Every change has an intent.md, spec.md and plan.md under `sdlc/changes/<id>/`, and the PR carries `Change: sdlc/changes/<id>`.
- Legacy record linkage follows `sourceOfTruth` in sdlc.config.json; the record carries the commit SHA.
- Approvals are recorded as merges/reviews by named humans; agents never approve.
## Segregation of duties
- The agent that produced a change cannot approve it. Code owner approval is required through branch protection.
- Production release requires a release manager's authorization (`RELEASE_APPROVAL`, CI environment approval).
## Regulated processes
- Changes touching <payments, claims decisions, credit decisions, medical records, personal data processing>
are `risk: high`: tech lead approval of spec.md and plan.md, plus <compliance sign-off> before release.
- Customer-facing copy that describes <fees, rights, terms> requires <legal/compliance> review: flag it.
## Records and retention
- Audit events for state changes: actor, action, entity, timestamp; retained <N years>.
- Do not delete or rewrite audit records, logs or historical artifacts; supersede them.
## Change management
- Emergency changes (incident tier 3σ) may bypass the spec stage only via a pre-approved runbook or a revert PR,
and must have a retrospective intent.md within <1 business day>.
- Scheduled maintenance windows: <policy>.
## How to apply
- spec.md: **Flagged concern** for every regulated touchpoint; owner = <compliance lead>.
- plan.md: the proof section names the audit events and tests that demonstrate compliance.
- review: policy breaches are **Important**; missing traceability is **Important**.From bibutikoley/ai-sdlc-claude, MIT.
More from bibutikoley/ai-sdlc-claude
- 0.564score
tracker-sync
bibutikoley
Keep the legacy tracker (Jira, YouTrack, GitLab issues, GitHub issues) and the Markdown artifacts linked according to sdlc.config.json sourceOfTruth (repo |…
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
security-policy
bibutikoley
The organisation's security policy as constraints on specs, plans, code and reviews.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
ux-standards
bibutikoley
Interaction, accessibility and content-structure standards for anything users touch.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
release
bibutikoley
Stage 5 (Deploy) release of the AI-native SDLC.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
review
bibutikoley
Stage 5 (Deploy) AI review of the AI-native SDLC.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
setup
bibutikoley
Install the AI-native SDLC loop into a product repository.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
spec
bibutikoley
Stage 2 (Design) of the AI-native SDLC.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
eval-add
bibutikoley
Stage 4 (Test) continuous evals.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
incident
bibutikoley
Stage 6 (Maintain) of the AI-native SDLC.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
intent
bibutikoley
Stage 1 (Plan) of the AI-native SDLC.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
metrics
bibutikoley
Compute and explain the AI-native SDLC's leading and lagging indicators from Git history, PR metadata and CI (intent time-to-commit, intent→spec, spec→plan…
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
plan
bibutikoley
Stage 3 (Build) entry of the AI-native SDLC.
SkillBFreshness: B★ 3Claude Code +9
Signals
- Stars
- 3
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Sep 5, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/bibutikoley/ai-sdlc-claude
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from bibutikoley
- 0.564score
plan
bibutikoley
Stage 3 (Build) entry of the AI-native SDLC.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
eval-add
bibutikoley
Stage 4 (Test) continuous evals.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
incident
bibutikoley
Stage 6 (Maintain) of the AI-native SDLC.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
intent
bibutikoley
Stage 1 (Plan) of the AI-native SDLC.
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
metrics
bibutikoley
Compute and explain the AI-native SDLC's leading and lagging indicators from Git history, PR metadata and CI (intent time-to-commit, intent→spec, spec→plan…
SkillBFreshness: B★ 3Claude Code +9 - 0.564score
brand-guidelines
bibutikoley
The organisation's brand and content standards applied to specs and UI work.
SkillBFreshness: B★ 3Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get compliance-policy running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
compliance-policy skill. Agent Mart. https://agentmart.dev/skills/bibutikoley-compliance-policy (last updated 2026-10-24)