003-skills-inventory
This Claude Code skill generates a comprehensive checklist document named INVENTORY-SKILLS-JAVA.md by extracting Java system prompt skills from a skills.xml source file and organizing them according to a predefined template structure. Use this skill when you need to create or update an inventory-driven checklist of Java skills, ensure complete coverage of all declared skills, or generate documentation that maps system prompts to specific Java development tasks within the cursor-rules-java project.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/003-skills-inventory && cp -r /tmp/003-skills-inventory/skills/003-skills-inventory ~/.claude/skills/003-skills-inventorySKILL.md
# Create a Checklist with all Java steps to use with system prompts for Java Create a comprehensive step-by-step checklist document for Java system prompts by following the embedded section template and deriving rows from `skills-generator/src/main/resources/skills.xml`. **What is covered in this Skill?** - Inventory-driven checklist generation - Output file creation as `INVENTORY-SKILLS-JAVA.md` - Strict coverage of every effective skill id declared in `skills.xml` ## Constraints Follow the template sections exactly and use `skills.xml` as the single source of truth for skill rows. - **DO NOT** create additional sections beyond what the template defines - **DO NOT** add skill rows absent from `skills.xml` - **DO NOT** omit any skill declared in `skills.xml` - **ONLY** use the `skillId` attribute as the generated skill id when it exists - **ONLY** use the single `reference-list/reference` value as the generated skill id when `skillId` is absent - **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 - Create Java system prompts checklist - Generate INVENTORY-SKILLS-JAVA.md - Use @003-skills-inventory ## Workflow 1. **Read the template and inventory source** Read `references/003-skills-inventory.md` and `skills-generator/src/main/resources/skills.xml` before generating output. Step constraints: - Do not use cached or remembered template content - Preserve exact section structure from the reference - Use `skillId` when present; otherwise use the single reference name 2. **Generate inventory document** Create `INVENTORY-SKILLS-JAVA.md` at the requested output path, or in the project root when no explicit path is requested, with one row for every effective skill id declared in `skills.xml`. 3. **Validate inventory coverage** Verify that the generated file contains every effective skill id from `skills.xml`, contains no extra skill rows, and preserves all expected sections from the reference. ## Reference For detailed guidance, examples, and constraints, see [references/003-skills-inventory.md](references/003-skills-inventory.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
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