Write an ADR

Create an ADR that records a real technical decision, then create the follow-up implementation issue that turns the decision into actionable work.

Prioritize context already available in the conversation and agent workspace. If the user has already described the bug, design conflict, or codebase problem, do not restart the interview. Distill the known context, explore only what is needed to verify it, and ask only blocking questions.

Both the ADR and follow-up issue must be junior-developer-ready: explain the decision, implementation sequence, verification steps, and risks clearly enough that a junior developer can execute the work without relying on hidden conversation context.

Process

1. Reconstruct the problem from current context

Start from the agent's existing context:

• User-provided bug reports, constraints, logs, screenshots, test failures, or design goals
• Codebase findings already gathered in the current session
• Prior implementation attempts, failed approaches, or known regressions
• Existing PRDs, issues, ADRs, docs, comments, or commit messages if relevant