Skip to main content
ClaudeWave
Skill435 repo starsupdated 3d ago

003-skills-inventory

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

Install in Claude Code
Copy
git clone --depth 1 https://github.com/jabrena/plinth /tmp/003-skills-inventory && cp -r /tmp/003-skills-inventory/skills/003-skills-inventory ~/.claude/skills/003-skills-inventory
Then start a new Claude Code session; the skill loads automatically.

SKILL.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 `plinth-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
- Inventory Java cursor rule skills
- List available Java system prompt skills

## Workflow

1. **Read the template and inventory source**

Read `references/003-skills-inventory.md` and `plinth-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).
openspec-proposeSkill

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.

001-commands-inventorySkill

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

002-agents-inventorySkill

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

004-commands-installationSkill

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

005-agents-installationSkill

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

012-agile-epicSkill

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

013-agile-featureSkill

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

014-agile-user-storySkill

Guides the creation of agile user stories. Use when the user wants to create a user story. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story; Split feature requirements into user stories. Part of Plinth Toolkit