Lintel on GitHub Copilot. Generated from skills/adr-new/SKILL.md; edit the canonical file, then run
li-copilot init.
- Resource root:
../../.. from this skill's base directory (the Lintel source with bin/,
lib/, skills/). Write plans, state and evidence into the working repository's .claude/
tree, never into the resource root.
- Skill-relative paths: this skill's own
scripts/, references/ and data/ folders (and a
<base> that the workflow defines as its own directory) mean
../../../skills/adr-new/ in the Lintel source, not this generated folder.
${LINTEL_SKILLS_DIR:-skills} means the skills root, ../../../skills. A bin/li-run step
runs in the working repository, so use $LINTEL_SKILLS_DIR/adr-new/ there.
- Shell steps: run Bash snippets with Bash (Git for Windows'
bash.exe on Windows, never
System32\bash.exe). Save a snippet to a temporary .sh file and run
bash "<resource root>/bin/li-run" <file>; it prepares LINTEL_SOURCE_ROOT, LINTEL_REPO_ROOT
and the profile context.
- Tools: Read=
view, Write=create, Edit=edit, Bash=bash/powershell, Grep=grep,
Glob=glob, AskUserQuestion=ask_user, TodoWrite=the plan checklist, Task or a named role=task
with that custom agent, WebFetch=web_fetch.
- Other Lintel workflows are native skills: invoke
/li-<name> rather than reading their
files. Named roles such as CodeReviewer are custom agents.
You are the adr-new skill.
When to use
- Non-trivial architectural decision being made
- Operator wants to record decision rationale durably
- Pattern emerges that future contributors should understand
- After /office-hours or /plan-eng-review session that produced a decision
When NOT to use
- Trivial decisions (file names, single-line config) — comment in code suffices
- Decisions that aren't final yet — wait until decision lands
- Replays of existing ADRs — update existing, don't create new
Workflow
Locate ADR directory. Check .claude/decisions/ exists. If not, recommend scaffolding init first.
Find next ADR number. Scan existing .claude/decisions/NNNN-*.md files. Next = max + 1.
Read template. .claude/decisions/TEMPLATE.md exists? If yes, load. If no, fall back to standard ADR format.
Gather context via ask_user (sequence):
- Title — one-line decision summary.
- Context — what is the situation that prompts this decision?
- Decision — what we will do.
- Alternatives considered — what else was on the table?
- Consequences — what becomes easier? Harder? What risks?
- Related ADRs — supersedes / informed by?
Generate slug. From title, kebab-case, ≤6 words.
Write ADR file. .claude/decisions/<NNNN>-<slug>.md. Status: Proposed by default.
Commit. Branch + commit:
git checkout -b adr-<NNNN>-<slug>
git add .claude/decisions/<NNNN>-<slug>.md
git commit -m "adr: <NNNN> <title>"
Report. Path + branch + next-step prompt.
Output format
ADR-NEW: <NNNN>-<slug>
Title: <title>
Status: Proposed
File: .claude/decisions/<NNNN>-<slug>.md
Branch: adr-<NNNN>-<slug>
Sections populated:
- ✓ Context
- ✓ Decision
- ✓ Alternatives
- ✓ Consequences
- ✓ Related ADRs
Next:
- [ ] Review draft
- [ ] git push + open PR
- [ ] Update status to "Accepted" when merged
Edge cases
- No
.claude/decisions/ directory — recommend bin/li-scaffold init first.
- Decision already documented in lessons.md — recommend cross-reference.
- Decision spans multiple repos — recommend ADR-as-RFC in shared design-docs repo.
- TEMPLATE.md custom — respect repo customization; load whatever's there.
ADR is part of session-harness
ADRs travel with the repo. Future Claude sessions read them at session-start (per CLAUDE.md). They're how decisions persist across sessions, across operators, and across years.
This skill is the bootstrap. Maintaining ADRs is operator-discipline.
1---2name: li-adr-new3description: Use when a non-trivial decision needs recording to bootstrap a new Architecture Decision Record from the template, asking context-gathering questions to fill Status, Context, Decision, and Consequences. Reach for it whenever you've made or are about to make an architectural choice worth a durable record.4metadata:5 source: https://skillmd.com/skills/jokerman89/li-adr-new6---78> **Lintel on GitHub Copilot.** Generated from `skills/adr-new/SKILL.md`; edit the canonical file, then run9> `li-copilot init`.10> - **Resource root:** `../../..` from this skill's base directory (the Lintel source with `bin/`,11> `lib/`, `skills/`). Write plans, state and evidence into the working repository's `.claude/`12> tree, never into the resource root.13> - **Skill-relative paths:** this skill's own `scripts/`, `references/` and `data/` folders (and a14> `<base>` that the workflow defines as its own directory) mean15> `../../../skills/adr-new/` in the Lintel source, not this generated folder.16> `${LINTEL_SKILLS_DIR:-skills}` means the skills root, `../../../skills`. A `bin/li-run` step17> runs in the working repository, so use `$LINTEL_SKILLS_DIR/adr-new/` there.18> - **Shell steps:** run Bash snippets with Bash (Git for Windows' `bash.exe` on Windows, never19> `System32\bash.exe`). Save a snippet to a temporary `.sh` file and run20> `bash "<resource root>/bin/li-run" <file>`; it prepares `LINTEL_SOURCE_ROOT`, `LINTEL_REPO_ROOT`21> and the profile context.22> - **Tools:** Read=`view`, Write=`create`, Edit=`edit`, Bash=`bash`/`powershell`, Grep=`grep`,23> Glob=`glob`, AskUserQuestion=`ask_user`, TodoWrite=the plan checklist, Task or a named role=`task`24> with that custom agent, WebFetch=`web_fetch`.25> - **Other Lintel workflows** are native skills: invoke `/li-<name>` rather than reading their26> files. Named roles such as `CodeReviewer` are custom agents.2728You are the adr-new skill.2930## When to use3132- Non-trivial architectural decision being made33- Operator wants to record decision rationale durably34- Pattern emerges that future contributors should understand35- After /office-hours or /plan-eng-review session that produced a decision3637## When NOT to use3839- Trivial decisions (file names, single-line config) — comment in code suffices40- Decisions that aren't final yet — wait until decision lands41- Replays of existing ADRs — update existing, don't create new4243## Workflow44451. **Locate ADR directory.** Check `.claude/decisions/` exists. If not, recommend scaffolding init first.46472. **Find next ADR number.** Scan existing `.claude/decisions/NNNN-*.md` files. Next = max + 1.48493. **Read template.** `.claude/decisions/TEMPLATE.md` exists? If yes, load. If no, fall back to standard ADR format.50514. **Gather context via ask_user (sequence):**5253 - **Title** — one-line decision summary.54 - **Context** — what is the situation that prompts this decision?55 - **Decision** — what we will do.56 - **Alternatives considered** — what else was on the table?57 - **Consequences** — what becomes easier? Harder? What risks?58 - **Related ADRs** — supersedes / informed by?59605. **Generate slug.** From title, kebab-case, ≤6 words.61626. **Write ADR file.** `.claude/decisions/<NNNN>-<slug>.md`. Status: Proposed by default.63647. **Commit.** Branch + commit:65 ```bash66 git checkout -b adr-<NNNN>-<slug>67 git add .claude/decisions/<NNNN>-<slug>.md68 git commit -m "adr: <NNNN> <title>"69 ```70718. **Report.** Path + branch + next-step prompt.7273## Output format7475```76ADR-NEW: <NNNN>-<slug>7778Title: <title>79Status: Proposed80File: .claude/decisions/<NNNN>-<slug>.md81Branch: adr-<NNNN>-<slug>8283Sections populated:84- ✓ Context85- ✓ Decision86- ✓ Alternatives87- ✓ Consequences88- ✓ Related ADRs8990Next:91- [ ] Review draft92- [ ] git push + open PR93- [ ] Update status to "Accepted" when merged94```9596## Edge cases9798- **No `.claude/decisions/` directory** — recommend `bin/li-scaffold init` first.99- **Decision already documented in lessons.md** — recommend cross-reference.100- **Decision spans multiple repos** — recommend ADR-as-RFC in shared design-docs repo.101- **TEMPLATE.md custom** — respect repo customization; load whatever's there.102103## ADR is part of session-harness104105ADRs travel with the repo. Future Claude sessions read them at session-start (per CLAUDE.md). They're how decisions persist across sessions, across operators, and across years.106107This skill is the bootstrap. Maintaining ADRs is operator-discipline.