Prompt file imported from JohnStrunk/advent-of-ai-2025 (
.github/prompts/madr.prompt.md). Fill in{{arguments}}before use. Copyright stays with the author.
Documenting a New Architectural Decision
The user input to you can be provided directly by the agent or as a command argument - you MUST consider it before proceeding with the prompt (if not empty).
User input:
{{arguments}}
The text the user typed after /madr in the triggering message is the
title of the decision record. Assume you always have it available in this
conversation even if {{arguments}} appears literally below. Do not ask the user
to repeat it unless they provided an empty command.
Follow these steps to create a new MADR (Markdown Architectural Decision
Record) file in the design/ directory.
- Run the script
design/new-record.sh -m "{{arguments}}"from reporoot and parse its JSON output for the filename. - Review the generated file to understand its structure and required sections.
- Review the other existing MADR files and feature description files in the
design/directory to understand how this new decision fits into the overall system architecture. - Engage in a back-and-forth dialogue with the user to gather detailed information about the decision. Ask clarifying questions to ensure all aspects are covered.
- Fill out each section of the MADR file with the information gathered, ensuring clarity and completeness.
- Continue to iterate and refine with the user until all template sections are adequately filled out and the decision fits within the overall system architecture.