030-architecture-adr-general
This skill guides users through an interactive conversation to create Architecture Decision Records (ADRs) for Java projects. It systematically gathers context, stakeholders, decision drivers, and options before generating a well-structured MADR-format ADR document. Use it when documenting architectural choices, evaluating technical alternatives, or recording framework, database, deployment, or infrastructure decisions.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/030-architecture-adr-general && cp -r /tmp/030-architecture-adr-general/skills/030-architecture-adr-general ~/.claude/skills/030-architecture-adr-generalSKILL.md
# 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. 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).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project