adrs

Use this agent when you need to write, revise, or iterate on an Architecture Decision Record (ADR). Delegate with clear instructions on what to write or edit -- it handles the actual authoring while the parent session retains architectural context. <example> Context: The orchestrating agent has resolved all open questions and gathered research. It delegates ADR authoring. user: "Write an ADR for replacing REST endpoints with GraphQL. Research is at adrs/1-pending/2026-04-02-graphql-migration/research.md. The chosen approach is schema-first with Apollo Server -- see the research for tradeoffs and rejected alternatives." assistant: 'I'll delegate to the adr-author agent to draft the ADR based on the completed research.' <commentary>The prompt gives the agent a concrete topic, points to the research file, and states the chosen approach so it can write without ambiguity.</commentary> </example> <example> Context: The user reviewed a draft ADR and wants changes. The orchestrating agent sends a revision request back to the same author agent. user: "Revise the ADR at adrs/1-pending/2026-04-02-graphql-migration/ADR.md. The user wants: (1) split the Implementation Roadmap into per-service migration steps, (2) add a risk entry for schema versioning, (3) cite the Apollo docs on federation." assistant: 'I'll send the revision instructions to the adr-author agent to update the draft.' <commentary>Revision prompts list specific changes so the agent does not need to guess scope. Sending to the same agent preserves writing context.</commentary> </example>

Use this agent to perform deep analysis of an existing project's architecture. Produces a comprehensive analysis report for downstream documentation authoring. <example> Context: The orchestrating agent needs a deep codebase analysis before writing architecture documentation. user: "Analyze the architecture of this project for documentation purposes" assistant: 'I'll delegate to the architecture-archaeologist to perform deep codebase analysis' <commentary>The archaeologist explores everything, identifies non-trivial decisions, researches their rationale, and produces a structured report.</commentary> </example>

Use this agent to write or update architecture documentation in the architecture/ directory. Delegate with clear instructions on what to write or edit. <example> Context: The orchestrating agent delegates full documentation authoring from a plan and research report. user: "Write the architecture docs based on the approved plan at [path] and the analysis report at [path]" assistant: 'I'll delegate to the architecture-author to draft the architecture documents' <commentary>Full documentation authoring from a plan and research.</commentary> </example> <example> Context: The orchestrating agent delegates a targeted update to an existing architecture document. user: "Update architecture/dependencies.md to reflect the new auth library added in the latest ADR" assistant: 'I'll send the update instructions to the architecture-author' <commentary>Simple targeted update to an existing document.</commentary> </example>

Drafts an Architecture Decision Record for a proposed change. Use when planning work that impacts project architecture.

Scaffold the adrs/ and architecture/ directory structure in the current project. Use when setting up ADRs for the first time.

Write initial architecture documentation for a project via deep codebase analysis. Use when a project lacks architecture docs or needs a comprehensive documentation baseline.

Guidelines for writing Architecture Decision Records (ADRs). Use when drafting or reviewing ADR content.

Guidelines and template for writing architecture README files. Defines the documentation hierarchy and README structure. Use when creating or updating an architecture/README.md file.