What inputs does the Architecture Decision Record Writer workflow use?

The workflow uses Decision. Required fields and their expected formats are listed on this page.

What resources are included in the Architecture Decision Record Writer blueprint?

The blueprint contains 2 AI agents, 0 functions, 0 MCP servers. Its workflow pattern is Dag.

All blueprints Engineering AI workflow blueprint

AI Architecture Decision Record Writer workflow blueprint

Describe a technical decision, get a formatted ADR with tradeoffs and alternatives

See where this blueprint fits in the production workflow lifecycle

Engineering

Documentation

Adr

Architecture

Request access

Pattern

Dag

Agents

2

Functions

0

MCP servers

0

Inputs for the Architecture Decision Record Writer workflow

Provide the following information when starting this workflow. Required inputs are validated before the first workflow stage runs.

Decision
Required
Description of the technical decision
Type: String

Input template

This request shape is generated from the blueprint's input schema. Angle-bracket values are placeholders; defaults and examples appear only when the source blueprint defines them.

{
  "decision": "<required string>"
}

How the Architecture Decision Record Writer AI workflow works

This engineering blueprint uses a dag workflow with 2 agents, 0 functions, and 0 MCP servers. This catalog blueprint is available by request; contact GraphN to discuss access and customization for your use case.

Context Gatherer
Agent using Context Gatherer
ADR Formatter
Agent using ADR Formatter

Blueprint resources and prerequisites

These are the actual agents, functions, and MCP servers declared by the blueprint. If an MCP server connects to an external system, configure the required connection and credentials in your GraphN workspace before running the workflow.

AI agent

Context Gatherer

Gather context for the decision: problem statement, constraints, alternatives, and stakeholder concerns.

AI agent

ADR Formatter

Format the decision into a standard ADR with Status, Context, Decision, Alternatives, Consequences sections.

Workflow output contract

The completed workflow makes the following output available to downstream steps, applications, or API clients:

Formatter

Frequently asked questions

What does the Architecture Decision Record Writer blueprint do?: Describe a technical decision, get a formatted ADR with tradeoffs and alternatives
What inputs does the Architecture Decision Record Writer workflow use?: The workflow uses Decision. Required fields and their expected formats are listed on this page.
What resources are included in the Architecture Decision Record Writer blueprint?: The blueprint contains 2 AI agents, 0 functions, 0 MCP servers. Its workflow pattern is Dag.
Can I customize the Architecture Decision Record Writer blueprint in GraphN?: This blueprint is currently available by request. Contact GraphN to discuss access and customization for your use case.

Related Engineering blueprints

View all software engineering workflows

API Data Summarizer

Fetch any public JSON API and get a clear, plain-language summary of the response

API Docs Generator

Point it at your API code and get OpenAPI-style docs with examples

Production Incident Response

Triage a production incident: analyze the alert, logs, and evidence in parallel and propose next steps

PR Diff Review

Review a code diff and get structured feedback on risks, bugs, and suggested changes