Sponsor Suno AI Music arrow_forward
Skill

001 Commands Inventory

Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing…

Type
Skill
Repository
jabrena/plinth
GitHub stars
441
License
Apache-2.0
Repo last updated
Sep 27, 2026
Source file
README.md

What 001 Commands Inventory is

001 Commands Inventory is a skill published in the jabrena/plinth repository on GitHub, which has about 441 stars. The repository describes itself as: “Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers.”

A skill is a folder with a SKILL.md file: frontmatter with a name and a description, followed by instructions Claude follows. Claude loads a skill automatically when a task matches its description, and you can also run it directly with a slash and its name.

Skills work in Claude Code and in Claude Cowork, which makes 001 Commands Inventory a portable way to give Claude the same method everywhere.

How to install 001 Commands Inventory

Claude Code

  1. Download the 001-commands-inventory folder from the repository.
  2. Save it as ~/.claude/skills/<skill-name>/SKILL.md for all projects, or .claude/skills/<skill-name>/SKILL.md for one project.
  3. Claude loads it automatically when a task matches; you can also run it with / and its name.

Claude Cowork

  1. Zip the skill folder so SKILL.md sits at the top level of the folder.
  2. Open Customize → Skills, click +, then upload the ZIP.
  3. Start a task that matches the description, or call it by name with /.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from README.md, shared under the repository's Apache-2.0 license. Read the full file on GitHub.

> Languages: Español · 中文 > > Help this project grow: Become a sponsor

Goal

An opinionated AI-native workflow for evolving modern Java Enterprise SDLC practices through reusable Skills, Agents, Commands & MCP servers.

What is a Plinth?

> A plinth represents the solid foundation or platform used to support statues or artworks in art and sculpture. It served as a structural and symbolic foundation for columns, statues, and entire temple podiums. Romans inherited the idea from Greek architecture but expanded its use to emphasize monumentality, hierarchy, and imperial power.

Project at a glance

  • 14 Commands
  • 9 Agents
  • 125 Skills

Latest Updates

Explore the latest published content on https://jabrena.github.io/plinth/ and follow its evolution through new skills, improvements, and fixes in the CHANGELOG.

Start in 60 seconds

Install every skill for your preferred agent:

npx skills add jabrena/plinth --skill '*' --agent cursor -y
npx skills add jabrena/plinth --skill '*' --agent claude-code -y
npx skills add jabrena/plinth --skill '*' --agent codex -y
npx skills add jabrena/plinth --skill '*' --agent github-copilot -y

Install every command for your prefered agent:

install @004-commands-installation cursor
install @004-commands-installation claude-code
install @004-commands-installation codex
install @004-commands-installation github-copilot

Install every agent for your prefered agent:

install @005-agents-installation cursor
install @005-agents-installation claude-code
install @005-agents-installation codex
install @005-agents-installation github-copilot

See it in action

You can use the project in 2 ways:

  • Use the AI-Native development workflow
  • Refactor your code with Skills

Using the AI-Native development workflow

Prepare the repository with /onboarding, then identify an issue in your Kanban dashboard from Atlasian Jira, Github Issues or Azure DevOps and apply the following workflow:

/onboarding
  |
  v
Issue
  |
  v
/update-issue --> /explore-problem --> /create-acceptance-criteria
  |
  v
/create-spec --> /explore-design
  |
  v
/implement-spec --> /close-spec

/onboarding establishes root AGENTS.md and one unambiguous OpenSpec project before issue selection. It preserves existing prerequisites; when OpenSpec is missing, you select its result path with documentation/openspec as the default.

##### Analysis & Design

Turn an idea into an actionable change with user stories, GitHub Issues or Jira, ADRs, diagrams, AI plan mode, and OpenSpec.

Functional Specification:

Command Explanation /onboarding Establish root repository guidance and one unambiguous OpenSpec project before issue work. /update-issue Update an existing GitHub or Jira issue with a structured user story, acceptance criteria, and resource content. /explore-problem Evaluate an issue from five perspectives and post a Functional Specification comment on the issue. /create-acceptance-criteria Derive Gherkin acceptance criteria from a Functional Specification and post them as a separate issue comment.

Technical Specification:

Command Explanation /create-adr (Optional) Record an architectural decision, its alternatives, rationale, and consequences. /create-diagram (Optional) Create a focused architecture or design diagram from approved artifacts. /create-spec (OpenSpec) Create or update one or more validated OpenSpec changes. /explore-design Compare technical approaches and obtain an approved design direction.

##### Build

Implement and improve Java applications with Maven, design, coding, testing, security, documentation, Spring Boot, Quarkus, Micronaut, OpenAPI, and WireMock guidance.

Command Explanation /implement-spec Deliver an approved plan or validated OpenSpec task list through framework-aware delegation. /close-spec Archive an OpenSpec change by name using the OpenSpec CLI.

Operate

Measure and improve production behavior through observability, profiling, benchmarking, and performance testing.

Command Explanation /profile Coordinate Java profiling from baseline detection through verified optimization. /benchmark Select and coordinate JMeter, Gatling, or JMH performance workflows.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is 001 Commands Inventory?

001 Commands Inventory is a skill for Claude Code and Claude Cowork from the jabrena/plinth repository on GitHub. Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing…

How do I install 001 Commands Inventory in Claude Code?

Download the 001-commands-inventory folder from the repository. Save it as ~/.claude/skills/<skill-name>/SKILL.md for all projects, or .claude/skills/<skill-name>/SKILL.md for one project. Claude loads it automatically when a task matches; you can also run it with / and its name.

Can I use 001 Commands Inventory in Claude Cowork?

Zip the skill folder so SKILL.md sits at the top level of the folder. Open Customize → Skills, click +, then upload the ZIP. Start a task that matches the description, or call it by name with /.

Is 001 Commands Inventory safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under Apache-2.0. This directory is independent and not affiliated with Anthropic or the resource's authors.