How do I install the File Adr skill?

Run npx skillmds@latest add thepictishbeast/file-adr 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 File Adr 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 File Adr?

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

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

Who published File Adr?

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

File Adr by thepictishbeast — Agent Skill

Name: File Adr
Author: thepictishbeast

File Adr

Scaffold a new Architecture Decision Record (Nygard format) + update the ADR index. Picks the next NNN number, writes the file with frontmatter + standard section skeleton, adds the row to docs/adr/README.md. Use when a non-trivial design decision needs explicit sign-off.

File contents

/file-adr — scaffold an ADR + update the index

Thin wrapper around the file-adr binary (installed at ~/.local/bin/file-adr; built by install.sh). Binary owns: next-number scan, file write, index-table update. Agent fills in the body.

Steps

Invoke the binary:

file-adr --slug <kebab-case-slug> \
         --title "<human-readable title>" \
         [--tracker <task-id-or-issue>] \
         [--status Proposed] \
         [--adr-dir docs/adr]

Stdout is the path of the new ADR file (e.g. docs/adr/019-foo.md). The binary also appends a row to docs/adr/README.md.

Open the new ADR file and fill in the body sections: Context · Decision framework · Proposal · Alternatives rejected · Acceptance criteria · Trade-offs accepted · Open questions for USER · Cross-references.
If the ADR closes a tracker task, mark that task in_progress via TaskUpdate (or completed if the ADR itself IS the deliverable).
Commit + push with message [ADR-NNN + #<tracker>] propose <decision>.

Net visible tool calls per ADR

3–5 total: Bash (file-adr) + Read (open file) + Edit/Write (fill body) + optional TaskUpdate + Bash (commit/push).

Down from ~8 in the prior manual flow (separate Write for ADR, Edit for README index, TaskUpdate, commit, push — plus mental overhead of picking the next number).

Constraints

--slug MUST be kebab-case lowercase ASCII (binary enforces).
--adr-dir defaults to docs/adr (per the LFI convention).
Status defaults to Proposed — change to Accepted only after USER sign-off, in a separate commit.

---name: file-adrdescription: Scaffold a new Architecture Decision Record (Nygard format) + update the ADR index. Picks the next NNN number, writes the file with frontmatter + standard section skeleton, adds the row to docs/adr/README.md. Use when a non-trivial design decision needs explicit sign-off.---# /file-adr — scaffold an ADR + update the indexThin wrapper around the `file-adr` binary (installed at`~/.local/bin/file-adr`; built by `install.sh`). Binary owns:next-number scan, file write, index-table update. Agent fills inthe body.## Steps1. **Invoke the binary**: ```sh file-adr --slug <kebab-case-slug> \ --title "<human-readable title>" \ [--tracker <task-id-or-issue>] \ [--status Proposed] \ [--adr-dir docs/adr] ``` Stdout is the path of the new ADR file (e.g. `docs/adr/019-foo.md`). The binary also appends a row to `docs/adr/README.md`.2. **Open the new ADR file and fill in the body sections**: Context · Decision framework · Proposal · Alternatives rejected · Acceptance criteria · Trade-offs accepted · Open questions for USER · Cross-references.3. **If the ADR closes a tracker task**, mark that task in_progress via TaskUpdate (or completed if the ADR itself IS the deliverable).4. **Commit + push** with message `[ADR-NNN + #<tracker>] propose <decision>`.## Net visible tool calls per ADR**3–5** total: `Bash` (file-adr) + `Read` (open file) + `Edit`/`Write`(fill body) + optional `TaskUpdate` + `Bash` (commit/push).Down from ~8 in the prior manual flow (separate Write for ADR,Edit for README index, TaskUpdate, commit, push — plus mentaloverhead of picking the next number).## Constraints- `--slug` MUST be kebab-case lowercase ASCII (binary enforces).- `--adr-dir` defaults to `docs/adr` (per the LFI convention).- Status defaults to `Proposed` — change to `Accepted` only after USER sign-off, in a separate commit.

Frequently asked questions