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 Toolkit
git clone --depth 1 https://github.com/jabrena/plinth /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 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).
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use @001-commands-inventory; Inventory embedded Java project commands; List command files bundled for Java agents. Part of Plinth Toolkit
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; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit
Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit
Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit
Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/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 .github/agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Bootstrap .codex/agents; Copy robot agents. Part of Plinth Toolkit
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 Plinth Toolkit
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; Break down an agile epic into deliverable features. Part of Plinth Toolkit