004-commands-installation
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
git clone --depth 1 https://github.com/jabrena/plinth /tmp/004-commands-installation && cp -r /tmp/004-commands-installation/skills/004-commands-installation ~/.claude/skills/004-commands-installationSKILL.md
# Embedded commands installer Install a predefined set of embedded project commands from repository assets into a user-selected target directory. This is an interactive skill. **What is covered in this Skill?** - Interactive target selection (`.github/commands`, `.claude/commands`, `.cursor/commands`, or `.codex/commands`) - Deterministic copy of all embedded commands defined via XInclude from `assets/commands` - Idempotent re-installation with clear overwrite reporting - Support for four command framework destinations ## Constraints This skill installs only the embedded project commands bundle and must ask for destination before writing files. - **MUST** ask the user to choose one of four command destinations before installing - **MUST** copy all embedded command files from skill `assets/commands/` - **MUST** preserve file names from the reference content and report overwrite actions - **MUST** create the destination directory if it does not exist ## When to use this skill - Install embedded commands - Bootstrap .cursor/command from project assets - Bootstrap .claude/commands from embedded commands - Copy project commands into .codex/commands - Install command suite into .github/commands ## Reference For detailed guidance, examples, and constraints, see [references/004-commands-installation.md](references/004-commands-installation.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 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