How do I install the Ce Adr Author skill?

Run npx skillmds add majiayu000/ce-adr-author in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ce Adr Author safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ce Adr Author?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ce Adr Author free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ce Adr Author?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ce Adr Author by majiayu000 — Agent Skill

Name: Ce Adr Author
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

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

Determine whether this is a new ADR or an update to an existing ADR.
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

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

Fill every required field and section in the template. Keep language normative when needed (MUST, MUST NOT, SHOULD).
Add/validate Related: ADR links and update references to superseded ADRs.
If the decision changes implementation sequencing, add a one-line summary in docs/improvement/RELEASE_PLAN_v1.md under ADR roadmap summary.
If status changes to Superseded, rename the replaced ADR with superseded prefix and set Superseded-by.

Status lifecycle

Status	Meaning
`Draft`	Under review; not yet binding
`Accepted`	Binding and enforceable
`Accepted (scoped)`	Binding only for explicit scope
`Deprecated`	Visible but replaced guidance exists
`Superseded`	Replaced 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:

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

---name: ce-adr-authordescription: Author or revise ADR files and release-plan ADR entries; use for new ADR drafts, status transitions, and ADR governance updates.--- # 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: ```bash Get-ChildItem docs/improvement/adrs/ADR-*.md | ForEach-Object { [int]($_.Name -replace 'ADR-(\d+).*','$1') } | Measure-Object -Maximum | Select-Object -ExpandProperty Maximum ``` 3. Copy the template asset to the target file: ```bash Copy-Item .claude/skills/ce-adr-author/assets/adr_template.md ` docs/improvement/adrs/ADR-<NNN>-<kebab-slug>.md ``` 4. Fill every required field and section in the template. Keep language normative when needed (`MUST`, `MUST NOT`, `SHOULD`). 5. Add/validate `Related:` ADR links and update references to superseded ADRs. 6. If the decision changes implementation sequencing, add a one-line summary in `docs/improvement/RELEASE_PLAN_v1.md` under ADR roadmap summary. 7. If status changes to `Superseded`, rename the replaced ADR with `superseded ` prefix and set `Superseded-by`. ## Status lifecycle | Status | Meaning | |---|---| | `Draft` | Under review; not yet binding | | `Accepted` | Binding and enforceable | | `Accepted (scoped)` | Binding only for explicit scope | | `Deprecated` | Visible but replaced guidance exists | | `Superseded` | Replaced 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`.

Frequently asked questions