OpenParable
Skip to content
← Back to skills

Ce Adr Author

Documents
ce-adr-author

Ce Adr Author is an Agent Skill for documents published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Author or revise ADR files and release-plan ADR entries; use for new ADR drafts, status transitions, and ADR governance updates.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/documents/ce-adr-author/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ce-adr-author, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

CE ADR Author

Use this skill for any architectural record work in docs/improvement/adrs/.

Core assets

  • assets/adr_template.md - canonical ADR template (copy this first).
  • docs/improvement/adrs/ - authoritative ADR directory.
  • docs/improvement/RELEASE_PLAN_v1.md - roadmap entry that must stay aligned.

Workflow

  1. Determine whether this is a new ADR or an update to an existing ADR.
  2. For new ADRs, calculate the next ADR number:
Get-ChildItem docs/improvement/adrs/ADR-*.md |
  ForEach-Object { [int]($_.Name -replace 'ADR-(\d+).*','$1') } |
  Measure-Object -Maximum | Select-Object -ExpandProperty Maximum
  1. Copy the template asset to the target file:
Copy-Item .claude/skills/ce-adr-author/assets/adr_template.md `
  docs/improvement/adrs/ADR-<NNN>-<kebab-slug>.md
  1. Fill every required field and section in the template. Keep language normative when needed (MUST, MUST NOT, SHOULD).
  2. Add/validate Related: ADR links and update references to superseded ADRs.
  3. If the decision changes implementation sequencing, add a one-line summary in docs/improvement/RELEASE_PLAN_v1.md under ADR roadmap summary.
  4. If status changes to Superseded, rename the replaced ADR with superseded prefix and set Superseded-by.

Status lifecycle

StatusMeaning
DraftUnder review; not yet binding
AcceptedBinding and enforceable
Accepted (scoped)Binding only for explicit scope
DeprecatedVisible but replaced guidance exists
SupersededReplaced by newer ADR

Required quality checks

  • Filename uses ADR-<NNN>-<kebab-slug>.md.
  • Template sections are complete (Context, Decision, Alternatives, Consequences, Adoption, Open Questions).
  • At least two alternatives are documented with rejection rationale.
  • Decision text states enforceable constraints clearly.
  • Related: entries point to real ADR files.
  • Release-plan linkage is updated when applicable.

Output contract

Return:

  1. ADR file path and status.
  2. Summary of decision and alternatives.
  3. Any companion updates made to RELEASE_PLAN_v1.md.