/030-architecture-adr-general
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
Claude Code
$ npx -y skills add jabrena/plinth --skill 030-architecture-adr-general --agent claude-code
Codex
$ npx skills add jabrena/plinth --skill 030-architecture-adr-general -a codex -y
Cursor
$ npx skills add jabrena/plinth --skill 030-architecture-adr-general -a cursor -y
Gemini CLI
$ npx skills add jabrena/plinth --skill 030-architecture-adr-general -a gemini-cli -y
GitHub Copilot
$ npx skills add jabrena/plinth --skill 030-architecture-adr-general -a github-copilot -y
OpenCode
$ npx skills add jabrena/plinth --skill 030-architecture-adr-general -a opencode -y
Windsurf
$ npx skills add jabrena/plinth --skill 030-architecture-adr-general -a windsurf -y
SKILL.md
030-architecture-adr-general.SKILL.mdname: 030-architecture-adr-general
description: 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 Plinth Toolkit
license: Apache-2.0
metadata:
author: Juan Antonio Breña Moral
version: 0.19.0
Java ADR Generator with interactive conversational approach
Generate Architecture Decision Records (ADRs) for Java projects through an interactive, conversational process that elicits the decision inputs needed for a well-structured ADR. **This is an interactive SKILL**. Use only the current conversation and repository files explicitly available in the current session; do not expose, persist, or reuse unrelated user/project context.
**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. **Load ADR reference and elicit decision inputs**
Load `references/030-architecture-adr-general.md` from this skill, then elicit stakeholders, decision drivers, options, and trade-offs through the current conversation only.
2. **Synthesize and confirm decision**
Summarize recommended option, rationale, and consequences, and confirm alignment with the user before creating the ADR artifact.
3. **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](references/030-architecture-adr-general.md).
Read more
name: 030-architecture-adr-general description: 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 Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0
Java ADR Generator with interactive conversational approach
Generate Architecture Decision Records (ADRs) for Java projects through an interactive, conversational process that elicits the decision inputs needed for a well-structured ADR. **This is an interactive SKILL**. Use only the current conversation and repository files explicitly available in the current session; do not expose, persist, or reuse unrelated user/project context.
**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. **Load ADR reference and elicit decision inputs**
Load `references/030-architecture-adr-general.md` from this skill, then elicit stakeholders, decision drivers, options, and trade-offs through the current conversation only.
2. **Synthesize and confirm decision**
Summarize recommended option, rationale, and consequences, and confirm alignment with the user before creating the ADR artifact.
3. **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](references/030-architecture-adr-general.md).
Other skills on plinth.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about 030-architecture-adr-general.
- Which coding agents can use 030-architecture-adr-general?
- 030-architecture-adr-general installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

