agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/030-architecture-adr-general/SKILL.md

030-architecture-adr-general

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

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

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands

    line 23
  2. Distinctive:

    EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with …

    line 24
  3. Distinctive:

    EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation …

    line 25
  4. Distinctive:

    Create Architecture Decision Record

    line 30
  5. Distinctive:

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

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

  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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free