003-agents-installation
This Claude Code skill interactively installs predefined embedded robot agent definitions into either `.cursor/agents` or `.claude/agents` directories. Use it when bootstrapping agent environments, copying robot agents to a project, or setting up the agent infrastructure for Java development workflows that require agent-based automation capabilities.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/003-agents-installation && cp -r /tmp/003-agents-installation/skills/003-agents-installation ~/.claude/skills/003-agents-installationSKILL.md
# Embedded agents installer Install a predefined set of embedded agent definitions from repository assets into a user-selected target directory. This is an interactive skill. **What is covered in this Skill?** - Interactive target selection (`.cursor/agents` or `.claude/agents`) - Deterministic copy of all embedded agents defined via XInclude from `assets/agents` - Idempotent re-installation with clear overwrite reporting ## Constraints This skill installs only the embedded robot agents bundle and must ask for destination before writing files. - **MUST** ask the user to choose `.cursor/agents` or `.claude/agents` before installing - **MUST** copy all embedded agent files defined in `references/003-agents-installation.md` - **MUST** preserve file names from the reference content and report overwrite actions ## When to use this skill - Install embedded agents - Bootstrap .cursor/agents - Bootstrap .claude/agents - Copy robot agents ## Workflow 1. **Choose destination** Ask exactly one question to choose `.cursor/agents` or `.claude/agents` and wait for an explicit answer before copying files. Step constraints: - Do not copy any file until destination is explicitly confirmed - If destination is ambiguous, ask a clarification question 2. **Install embedded agents** Create the destination directory if needed, then copy all embedded agent files defined in the reference content, preserving filenames and warning before overwriting existing files. 3. **Report installation result** Return a concise checklist with selected destination, created/updated files, overwrite actions, and an optional verification command. ## Reference For detailed guidance, examples, and constraints, see [references/003-agents-installation.md](references/003-agents-installation.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
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
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
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