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
67
—
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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?
Handle ambiguity and blockers explicitly to avoid implicit assumptions.
Load references/030-architecture-adr-general.md from this skill, then elicit stakeholders, decision drivers, options, and trade-offs through the current conversation only.
Summarize recommended option, rationale, and consequences, and confirm alignment with the user before creating the ADR artifact.
Create a MADR-style ADR document with the final decision, alternatives, consequences, and follow-up actions.
For detailed guidance, examples, and constraints, see references/030-architecture-adr-general.md.
86eb63d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.