Yes. You can use existing ADRs, but they must follow the expected naming and metadata format for the tool to recognize them properly. Consider running migrate to align them with the latest configuration.
No. AdrPlus manages ADR Markdown files and can be used in repositories of any language or framework.
Yes. If scopes are enabled, ADRs with the same title can coexist as long as they are in different scopes.
On first use, the initial setup wizard runs automatically when you execute any command (except help). This ensures your configuration is set up correctly.
After the initial setup is complete, the interactive wizard (--wizard) is optional for subsequent commands. You can run commands directly with their arguments without using the wizard.
adrplus.json.
adr-config.adrplus.
Yes. Language is configurable (for example, en-US and pt-BR).
The behavior is controlled by the WithoutArgs setting in adrplus.json:
Help(default): Displays the help information with all available commandsWizard: Launches the interactive wizard for guided operationsNone: Requires you to explicitly provide a command; otherwise, an error is shown
You can change this behavior anytime by running adrplus config --application.
No. You cannot customize ADR headers directly. You can customize status labels and header names in adr-config.adrplus using keys such as statusnew, statusacc, statusrej, statussup, headerstatus, headerversion, and headerrevision.
Yes. You can customize status labels in adr-config.adrplus with statusnew, statusacc, statusrej, and statussup.
Yes. Set folderbyscope to true but ensure your workflow and team conventions align with this structure.
When scope is enabled and the selected scope is not listed in skipdomain.
No. The date format is fixed in the tool's metadata handling and cannot be customized.
version: creates a new major version of the same ADR sequence.review: creates a revision of the same ADR version (when revision is enabled).supersede: creates a successor ADR with a new sequence number.
The tool scans existing ADR files, finds the highest sequence number, and increments it by one.
Yes. Pass arguments directly (for example, --title, --file, --path).
Yes. It follows the integrated status and naming workflow and reports in the header of the replaced ADR that a replacement exists.
No. This version focuses on core ADR fields. You can include additional information in the ADR content as needed.
Not as separate integrated template files, however the tool uses the template in the configuration file in each repository. In this scenario, you can use the tool without having to configure the template that has already been agreed upon by the team.
Deleting ADR files can break traceability. Prefer reject or supersede.
The tool blocks the action. Use undo first, then approve if applicable.
Concurrent changes may cause numbering conflicts; resolve via normal Git merge/rebase flow.
Use repository practices (branch policies, code owners, reviews) to control concurrent edits.
Commands that depend on repository config can fail until the file is fixed.
Yes. Use scopes to organize ADRs by project, and ensure your team conventions align with this structure.