Menu
Create an Architectural Decision Record (ADR) under documentation/docs/adr/. Use when making or documenting an architectural decision.
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
| name | adr |
| description | Create an Architectural Decision Record (ADR) under documentation/docs/adr/. Use when making or documenting an architectural decision. |
Create an ADR document for the Cosmian KMS repository.
Save ADRs at: documentation/docs/adr/adr-NNNN-[title-slug].md
Where NNNN is the next sequential 4-digit number. Check existing files to determine the next number:
ls documentation/docs/adr/ 2>/dev/null | sort | tail -5
If the documentation/docs/adr/ directory doesn't exist yet, create it and add a nav entry in documentation/mkdocs.yml.
Ask the user for:
If any required input is missing, ask before proceeding.
---
title: "ADR-NNNN: [Decision Title]"
status: "Proposed"
date: "YYYY-MM-DD"
authors: "[Stakeholder Names/Roles]"
tags: ["architecture", "decision"]
supersedes: ""
superseded_by: ""
---
# ADR-NNNN: [Decision Title]
## Status
**Proposed** | Accepted | Rejected | Superseded | Deprecated
## Context
[Problem statement, technical constraints, business requirements, and environmental factors requiring this decision.]
## Decision
[Chosen solution with clear rationale for selection.]
## Consequences
### Positive
- **POS-001**: [Beneficial outcome]
- **POS-002**: [Performance, maintainability, or security improvement]
### Negative
- **NEG-001**: [Trade-off or limitation]
- **NEG-002**: [Technical debt or complexity introduced]
## Alternatives Considered
### [Alternative 1 Name]
- **ALT-001 Description**: [Brief technical description]
- **ALT-002 Rejection Reason**: [Why this option was not selected]
### [Alternative 2 Name]
- **ALT-003 Description**: [Brief technical description]
- **ALT-004 Rejection Reason**: [Why this option was not selected]
## Implementation Notes
- **IMP-001**: [Key implementation consideration]
- **IMP-002**: [Migration or rollout strategy if applicable]
- **IMP-003**: [Monitoring and success criteria]
## References
- **REF-001**: [Related ADRs or prior decisions]
- **REF-002**: [External documentation, RFCs, specifications]
- **REF-003**: [Relevant codebase files: e.g. `crate/server_database/src/`, `crate/server/src/config/`]
documentation/mkdocs.yml to include the new ADR under the ADRs nav section (create the section if it doesn't exist).docs(adr): add ADR-NNNN [title]Write the next version entry at the top of CHANGELOG.md by summarizing all changes since the last tagged release. Use when preparing release notes.
Audit GitHub Actions workflows for efficiency and recommend fixes to reduce CI minutes and costs. Use when asked to improve CI performance.
Fix CI failures in a loop until all GitHub workflow runs on the current branch are green. Use when CI is failing and needs automated repair.
AI-powered security scanner — OWASP Top 10, CWE Top 25, KMIP authorization, FIPS gating, memory safety, side-channel, supply chain, and 20 vulnerability families. Use when asked to review code security, audit KMIP access control, or scan for vulnerabilities.
Comprehensive cryptographic audit: FIPS 140-3, BSI TR-02102, ANSSI, NIST SP 800-series compliance, algorithm allow-list, key sizes, feature-flag gating, OpenSSL provider init, key lifecycle, multi-standard matrix, and academic cryptanalysis cross-check. Use when touching crate/crypto/, algorithm selection, or key management code.
Comprehensive security audit orchestrator: invokes /security-review, /cryptography-review, /threat-model, and /standards-review in sequence. Produces a unified go/no-go report. Use for full security audit before release or after significant changes.