OpenParable
Skip to content
← Back to skills

030 Architecture Adr General

Documents
030-architecture-adr-general

030 Architecture Adr General is an Agent Skill for documents published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/development/030-architecture-adr-general/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/030-architecture-adr-general, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Java ADR Generator with interactive conversational approach

Generate Architecture Decision Records (ADRs) for Java projects through an interactive, conversational process that systematically gathers all necessary context to produce well-structured ADR documents. This is an interactive SKILL.

What is covered in this Skill?

  • ADR file storage configuration
  • Conversational information gathering: context, stakeholders, decision drivers, options with pros/cons, outcome, consequences
  • MADR template generation

Constraints

Handle ambiguity and blockers explicitly to avoid implicit assumptions.

  • EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
  • EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
  • EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off

When to use this skill

  • Generate ADR
  • Create Architecture Decision Record
  • Document architecture decision
  • Architecture Decision Record for Java
  • Write ADR
  • Document technical decision
  • Architecture documentation
  • Record design decision
  • Technology choice documentation
  • Framework selection ADR
  • Database choice ADR
  • Architectural trade-offs
  • Technical alternatives evaluation
  • Why did we choose
  • Deployment strategy ADR
  • Infrastructure choice
  • Vendor selection ADR

Workflow

  1. Read ADR reference and gather context

Read references/030-architecture-adr-general.md, then collect context, stakeholders, decision drivers, options, and trade-offs through conversation.

  1. Synthesize and confirm decision

Summarize recommended option, rationale, and consequences, and confirm alignment with the user before creating the ADR artifact.

  1. Generate ADR output

Create a MADR-style ADR document with the final decision, alternatives, consequences, and follow-up actions.

Reference

For detailed guidance, examples, and constraints, see references/030-architecture-adr-general.md.