002-agents-inventory
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
git clone --depth 1 https://github.com/jabrena/plinth /tmp/002-agents-inventory && cp -r /tmp/002-agents-inventory/skills/002-agents-inventory ~/.claude/skills/002-agents-inventorySKILL.md
# Create a Checklist with embedded agents inventory for Java Create a comprehensive checklist document for embedded agents inventory by following the embedded template exactly. **What is covered in this Skill?** - Exact-template checklist generation - Output file creation as `INVENTORY-AGENTS-JAVA.md` - Strict adherence to listed sections and content ## Constraints Follow the template exactly without adding or removing sections, rows, or details. - **DO NOT** create additional rows beyond what the template defines - **DO NOT** add agent entries not explicitly listed in the template - **ONLY** use exact wording and structure from the embedded template - **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 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 ## Workflow 1. **Read the embedded template** Read `references/002-agents-inventory.md` before generating output and use it as the authoritative template. Step constraints: - Do not use cached or partial template content - Preserve exact table rows, headings, and structure from the reference 2. **Generate inventory document** Create `INVENTORY-AGENTS-JAVA.md` in the project root using the exact wording and ordering from the reference template. 3. **Validate template fidelity** Confirm no extra agent rows were introduced and all required reference sections are present in the generated file. ## Reference For detailed guidance, examples, and constraints, see [references/002-agents-inventory.md](references/002-agents-inventory.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 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
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