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 requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of Plinth ToolkitFrom its SKILL.md
npx -y skills add jabrena/plinth --skill 030-architecture-adr-generalAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.9 KB, as published. Nobody here has run it
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
- 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.
- Synthesize and confirm decision
Summarize recommended option, rationale, and consequences, and confirm alignment with the user before creating the ADR artifact.
- 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.
What ships with it: 1 file
18.4 KB alongside SKILL.md
references/
Gives 0 of the 12 instructions most architecture codebase skills give
Counted across 858 of the 1,304 authors here whose files we hold, read 2026-09-06
- Apply the deletion test to identify shallow modulesin 32 of 858, across 31 files
- Read domain glossary and ADRs before exploringin 22 of 858, across 19 files
- Use Tailwind and Mermaid via CDN for reportsin 21 of 858, across 18 files
- Document architecture decision recordsin 20 of 858, across 12 files
- Offer to record ADRs for rejected candidatesin 17 of 858, across 14 files
- Limit primary navigation to four to seven itemsin 17 of 858, across 7 files
- Write HTML report to the system temp directoryin 17 of 858, across 14 files
- Read product marketing context before asking questionsin 16 of 858, across 6 files
- Use Mermaid graph TD for visual sitemapsin 15 of 858, across 5 files
- Ensure every page has at least one internal linkin 15 of 858, across 5 files
- Use ASCII tree format for page hierarchy draftsin 15 of 858, across 5 files
- Enforce lowercase URLs with hyphensin 15 of 858, across 5 files
Said here and by no other author read
- Report missing context or tools as blockers
- Explain conflicts with project constraints
- Elicit stakeholders and decision drivers
- Summarize recommended options and rationale
- Confirm alignment before creating artifacts
- Generate MADR style documentation
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.