How do I install the Adr Writer skill?

Run npx skillmds@latest add stark-ai-de/adr-writer 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 Adr Writer safe to use?

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

Which AI agents work with Adr Writer?

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 Adr Writer free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Adr Writer?

stark-ai-de (@stark-ai-de) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Adr Writer by stark-ai-de — Agent Skill

Name: Adr Writer
Author: stark-ai-de

Adr Writer

Create short Architecture Decision Records under docs/adr. Use when the user makes a repo-level decision, changes skill format, publishing, validation, license, layout, or maintainer policy, and wants a concise ADR without documentation bloat.

stark-ai-de Updated Sep 17, 2026

File contents

ADR Writer

Goal

Create a short Architecture Decision Record that captures one repo-level decision without turning it into long-form documentation.

When to use

A decision changes repo structure, publishing, validation, license, layout, or skill standards.
A previous ADR is superseded, deprecated, or rejected.
The user asks to document a repo-level decision.

When not to use

Tiny copy edits, typo fixes, or minor template polish.
Routine skill additions that follow existing standards.
Temporary implementation details that do not affect future maintainers.

Inputs to inspect

docs/adr/README.md
docs/adr/TEMPLATE.md
Existing docs/adr/NNNN-*.md files
The decision context, current repo docs, and validation requirements

Workflow

Identify the single decision sentence.
Check docs/adr/README.md and the latest ADR number.
Create the next docs/adr/NNNN-short-title.md.
Use docs/adr/TEMPLATE.md or incubator/skills/repo-maintenance/adr-writer/assets/adr-template.md.
Keep the ADR under 250 words, with a target of 120 to 180 words.
Update the ADR index in docs/adr/README.md.
Run ADR validation.

Safety rules

Do not write long ADRs.
Do not rewrite accepted ADRs; create a superseding ADR instead.
Do not document secrets, private internal details, customer data, or credentials.
Do not invent decision history. Mark uncertain decisions as Proposed.

References

Read only when needed:

assets/adr-template.md for the compact ADR template.

Scripts

Use only when the user wants a new ADR file created:

npm run adr:new -- "Use category-based skill folders"

Output format

Return:

ADR path
Decision sentence
Word count
Validation result
Recommended next action

Completion criteria

The ADR records exactly one repo-level decision.
The ADR is under 250 words.
The ADR index is updated.
ADR validation passes.

Failure modes

If the decision is unclear, ask for the decision sentence before writing.
If the next ADR number cannot be determined, stop and report the conflicting files.
If validation fails, report the failing ADR rule and the file path.

---name: adr-writerdescription: Create short Architecture Decision Records under docs/adr. Use when the user makes a repo-level decision, changes skill format, publishing, validation, license, layout, or maintainer policy, and wants a concise ADR without documentation bloat.license: Apache-2.0---# ADR Writer## GoalCreate a short Architecture Decision Record that captures one repo-level decision without turning it into long-form documentation.## When to use- A decision changes repo structure, publishing, validation, license, layout, or skill standards.- A previous ADR is superseded, deprecated, or rejected.- The user asks to document a repo-level decision.## When not to use- Tiny copy edits, typo fixes, or minor template polish.- Routine skill additions that follow existing standards.- Temporary implementation details that do not affect future maintainers.## Inputs to inspect- `docs/adr/README.md`- `docs/adr/TEMPLATE.md`- Existing `docs/adr/NNNN-*.md` files- The decision context, current repo docs, and validation requirements## Workflow1. Identify the single decision sentence.2. Check `docs/adr/README.md` and the latest ADR number.3. Create the next `docs/adr/NNNN-short-title.md`.4. Use `docs/adr/TEMPLATE.md` or `incubator/skills/repo-maintenance/adr-writer/assets/adr-template.md`.5. Keep the ADR under 250 words, with a target of 120 to 180 words.6. Update the ADR index in `docs/adr/README.md`.7. Run ADR validation.## Safety rules- Do not write long ADRs.- Do not rewrite accepted ADRs; create a superseding ADR instead.- Do not document secrets, private internal details, customer data, or credentials.- Do not invent decision history. Mark uncertain decisions as `Proposed`.## ReferencesRead only when needed:- `assets/adr-template.md` for the compact ADR template.## ScriptsUse only when the user wants a new ADR file created:```bashnpm run adr:new -- "Use category-based skill folders"```## Output formatReturn:1. ADR path2. Decision sentence3. Word count4. Validation result5. Recommended next action## Completion criteria- The ADR records exactly one repo-level decision.- The ADR is under 250 words.- The ADR index is updated.- ADR validation passes.## Failure modes- If the decision is unclear, ask for the decision sentence before writing.- If the next ADR number cannot be determined, stop and report the conflicting files.- If validation fails, report the failing ADR rule and the file path.

Frequently asked questions