jabrena/plinth

> **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:
Install every command for your prefered agent:
Install every agent for your prefered agent:
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 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.
Compliance (Alpha)
Review Java systems, AI models, and how GenAI tools are used across applications and delivery pipelines for regulation-aware engineering controls, evidence, and qualified owner handoffs spanning AI, data, security, product, platform, market, and governance. ** These skills support engineering awareness and do not provide legal advice. **