Skip to content

feat: create ADR templates#2166

Draft
elnelson575 wants to merge 2 commits intomainfrom
feat/adr_setup
Draft

feat: create ADR templates#2166
elnelson575 wants to merge 2 commits intomainfrom
feat/adr_setup

Conversation

@elnelson575
Copy link
Contributor

A CLAUDE.md or .claude/CLAUDE.md should explain how Claude should interact with the ADR and folder structure.

Within the ADR folder or subfolders, we should have a REAMDE.md to explain the ADRs within that folder or nested folders.

adr/README.md
adr/_template.md
adr/0123-<EPIC_NAME>.md

doc/ is already taken for quartodocs, so we use adr/ as the root dir.

ADRs should follow: https://github.com/joelparkerhenderson/architecture-decision-record/tree/main/locales/en/templates/decision-record-template-of-the-madr-project

We should define some .claude/commands/NAME.md (ex: adr-init.md) to do some commands like:
Create an ADR from a plan, given one by the user: {ask for a plan}
Create an ADR from Claude's currently in-use plan: {use the current plan}
Guide the user through an interview to create an ADR about a past decision: {interview us on a plan}

Make a plan to:
Create a root folder `CLAUDE.md` or `.claude/CLAUDE.md` is good. It should explain how claude is to interact and folder structures.

Within some folder... we can have a `REAMDE.md` to explain the ADRs within that folder or nested folders.

```javascript
/doc/adr/README.md
/doc/adr/_template.md
/doc/adr/0123-<EPIC_NAME>.md

ADRs should follow: https://github.com/joelparkerhenderson/architecture-decision-record/tree/main/locales/en/templates/decision-record-template-of-the-madr-project

They should sit in doc/adr as the default folder.  
We should define some .claude/commands/NAME.md (ex: adr-init.md) to do some commands like:
Create an ADR from a plan, given one by the user: {ask for a plan}
Create an ADR from Claude's currently in-use plan: {use the current plan}
Guide the user through an interview to create an ADR about a past decision: {interview us on a plan}
```
Make a plan to:
Create a root folder `CLAUDE.md` or `.claude/CLAUDE.md` is good. It should explain how claude is to interact and folder structures.

Within some folder... we can have a `REAMDE.md` to explain the ADRs within that folder or nested folders.

```javascript
/doc/adr/README.md
/doc/adr/_template.md
/doc/adr/0123-<EPIC_NAME>.md

ADRs should follow: https://github.com/joelparkerhenderson/architecture-decision-record/tree/main/locales/en/templates/decision-record-template-of-the-madr-project

They should sit in doc/adr as the default folder. 
We should define some .claude/commands/NAME.md (ex: adr-init.md) to do some commands like:
Create an ADR from a plan, given one by the user: {ask for a plan}
Create an ADR from Claude's currently in-use plan: {use the current plan}
Guide the user through an interview to create an ADR about a past decision: {interview us on a plan}
```
@elnelson575 elnelson575 changed the title Create ADR plan (vibe-kanban 7aba524c) Create ADR templates Feb 11, 2026
@elnelson575 elnelson575 changed the title Create ADR templates feat: create ADR templates Feb 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant