Use Autohand Code with technical writing skill guidance to turn design discussions and code context into ADRs that stay useful after implementation.
Capture decisions, alternatives, and consequences
Documentation Discovery and planning Planning Docs
autohand -p "Write an ADR for this architecture decision using the repo context, alternatives, and consequences"
An ADR with context, decision, alternatives, consequences, and links to validating code or docs.
Write architecture decision records with Autohand Code is a technical-writing workflow that captures architecture context, decision, alternatives, consequences, validation evidence, and follow-up ownership in an ADR. ### At a glance | Question | Answer | | --- | --- | | Best for | database choices, service boundaries, framework migrations, integration standards, and decisions that future maintainers will question | | Primary inputs | Decision prompt, considered alternatives, and chosen path; Relevant files, diagrams, issues, or meeting notes; Constraints, risks, owners, and validation evidence | | Autohand Code returns | An ADR with context, decision, alternatives, consequences, and links to validating code or docs. | | Avoid when | the team has not made a decision or there is no implementation context to cite | ### How Autohand Code handles this workflow 1. Reads the implementation context and existing docs style. 2. Separates confirmed constraints from assumptions. 3. Writes the ADR with alternatives and consequences that matter to maintainers. 4. Links to code, tests, docs, or rollout evidence reviewers can inspect. ### Best inputs - Decision prompt, considered alternatives, and chosen path - Relevant files, diagrams, issues, or meeting notes - Constraints, risks, owners, and validation evidence ### Strong prompt autohand -p "Write an ADR for this architecture decision using the repo context, alternatives, and consequences" ### Autohand Code CLI options - Use `/skills use technical-writing` for ADR and architecture doc structure. - Run `autohand -p "Write an ADR for this architecture decision using the repo context, alternatives, and consequences"` with the decision notes. - Use `--patch` if the ADR should be reviewed as a docs-only diff before applying. ### Review before accepting A good ADR includes context, decision, rejected alternatives, consequences, validation links, and owner follow-ups. ### Source and validation signals Autohand AI maintains this workflow as first-party product guidance for Autohand Code. Use the [Autohand CLI Playbook](https://github.com/autohandai/code-cli/blob/main/docs/AUTOHAND_PLAYBOOK.md), [CLI reference](/docs/working-with-autohand-code/cli-reference.html), and [configuration reference](https://github.com/autohandai/code-cli/blob/main/docs/config-reference.md) when choosing between interactive mode, command mode, auto-mode, feature-enabled /goal, /settings, skills, MCP, and permission settings. The related resources below link to product docs and tutorials for the workflow, and the final answer should name repository-specific files, commands, outputs, or docs that a reviewer can verify. ### Frequently asked questions ### What is Write architecture decision records with Autohand Code? Write architecture decision records with Autohand Code is a technical-writing workflow that captures architecture context, decision, alternatives, consequences, validation evidence, and follow-up ownership in an ADR. ### When should a team use Write architecture decision records? Use it when a technical decision needs to outlive the chat, meeting, or pull request where it was made. ### What evidence should reviewers check for Write architecture decision records? A good ADR includes context, decision, rejected alternatives, consequences, validation links, and owner follow-ups.
Skill Skilled: Technical Writing Use technical documentation and spec-writing guidance. https://skilled.autohand.ai/skill/technical-writing Guide Maintaining Documentation Keep docs aligned with code changes. /docs/guides/maintaining-documentation.html Reference Plan Mode Plan docs alongside implementation. /docs/working-with-autohand-code/plan-mode.html