create-adr

You can document architectural decisions in the MADR format by using a skill that interactively gathers context, decision, and consequences, then writes the completed record to your project's docs directory. It automatically numbers the file and generates a slug from your title.

To generate ADR filenames and numbers automatically, this skill determines the next sequential number and derives a kebab-case filename slug directly from the decision title you provide, ensuring consistent naming conventions without manual tracking.

Yes, the skill validates the existence of the ADR directory and template file before drafting. It checks for the required project documentation structure in the docs/adr/ path to ensure proper formatting before writing.

Yes, you can review the draft before it is saved. The skill interactively prompts you for the essential ADR sections and presents a complete draft for your confirmation and approval before writing the file to the directory.

You need to write an Architectural Decision Record when your team makes significant technical choices, such as adopting a new library for asynchronous tasks, to systematically document the context, alternatives considered, and consequences for future maintainability.