Conversation
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} ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A
CLAUDE.mdor.claude/CLAUDE.mdshould explain how Claude should interact with the ADR and folder structure.Within the ADR folder or subfolders, we should have a
REAMDE.mdto explain the ADRs within that folder or nested folders.doc/is already taken for quartodocs, so we useadr/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}