Plinth skill for Codex

Skills (126)

• 001-commands-inventory — 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…
• 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…
• 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…
• 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…
• 005-agents-installation — 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…
• 012-agile-epic — 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…
• 013-agile-feature — 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…
• 014-agile-user-story — 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…
• 021-problem-framing — Use when a problem or issue needs explicit framing before deeper analysis begins — establishing the Problem statement, Current state, Desired state, Stakeholders, and Success criteria. This should trigger when an issue's Problem Framing point of view needs…
• 022-root-cause-analysis — Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification. This should trigger when an issue's Root Cause Analysis point of view…
• 023-assumption-analysis — Use when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan. This should trigger when an issue's Assumption Analysis point of view needs evaluation, or…
• 024-context-mapping — Use when a problem under exploration needs its surrounding system context identified before design begins — Existing systems, Integrations, Ownership, and External dependencies. This should trigger when an issue's Context Mapping point of view needs…
• 025-quality-attribute-discovery — Use when a problem under exploration needs its quality attributes (non-functional requirements) identified and prioritized before architecture and design begin. This should trigger when an issue's Quality Attribute Discovery point of view needs evaluation…
• 030-architecture-adr-general — Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This…
• 033-architecture-diagrams — Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams, ER (Entity Relationship) diagrams, and bounded-context diagrams — through a…
• 041-planning-plan-mode — Use when creating or refining a structured Java implementation plan from trusted issue summaries, approved designs, ADRs, OpenSpec changes, existing plans, or a valid combination. The plan records its source artifacts and derivation direction and can remain…
• 042-planning-openspec — Use when creating or updating OpenSpec artifacts from an issue, plan, approved design, ADRs, existing OpenSpec, or a valid combination. The workflow assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent…
• 043-planning-github-issues — Use when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use…
• 044-planning-jira — Use when you need Jira CLI (`jira`) installation/authentication guidance and a maintainer-authored Jira issue inventory workflow. The agent does not ingest raw Jira issue or JQL output directly; it asks the Jira project maintainer/operator to author…
• 045-planning-azure-devops — Use when you need Azure DevOps CLI guidance to verify installation, configure organization and project context, discover work item IDs by optional WIQL filters, and execute safe work-item create/update operations. Uses an interactive install gate - if `az`…
• 051-design-two-steps-methods — Use when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then making the intended behavior change once the design supports it. This should…
• 052-design-hamburger-method — Use when a large feature, story, plan, or spec idea needs to be split into small vertical slices with the Hamburger Method. This should trigger for requests such as Split this oversized story; Find the smallest useful slice; Break this feature into vertical…
• 053-design-simple-rules — Use when Java design, refactoring, or implementation tradeoffs should be evaluated with Kent Beck's simple design rules, including passes the tests, reveals intention, has no duplication, and has the fewest elements. This should trigger for requests such as…
• 054-design-tdd — Use when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests…
• 055-design-parallel-change — Use when a database schema or data-meaning change needs Parallel Change, including expand, migrate, and contract sequencing for column renames, type or data reinterpretation, large-table backfills, relationship-table changes, enum/status transitions…
• 056-design-avoid-breaking-changes
• 057-design-feature-toggles
• 058-design-bdd
• 059-design-atdd
• 110-java-maven-best-practices
• 111-java-maven-dependencies
• 112-java-maven-plugins
• 113-java-maven-documentation
• 114-java-maven-search
• 121-java-object-oriented-design
• 122-java-type-design
• 123-java-design-patterns
• 124-java-secure-coding
• 125-java-concurrency
• 126-java-exception-handling
• 128-java-generics
• 130-java-testing-strategies
• 131-java-testing-unit-testing
• 132-java-testing-integration-testing
• 133-java-testing-acceptance-tests
• 141-java-refactoring-with-modern-features
• 142-java-functional-programming
• 143-java-functional-exception-handling
• 144-java-data-oriented-programming
• 145-java-refactoring-high-performance
• 151-java-performance-jmeter
• 152-java-performance-gatling
• 161-java-profiling-detect
• 162-java-profiling-analyze
• 163-java-profiling-refactor
• 164-java-profiling-verify
• 170-java-documentation
• 181-java-observability-logging
• 182-java-observability-metrics-micrometer
• 183-java-observability-tracing-opentelemetry
• 200-agents-md
• 300-frameworks-spring-boot-create-project
• 301-frameworks-spring-boot-core
• 302-frameworks-spring-boot-rest
• 303-frameworks-spring-boot-validation
• 304-frameworks-spring-boot-security
• 305-frameworks-spring-boot-modulith
• 311-frameworks-spring-jdbc
• 312-frameworks-spring-data-jdbc
• 313-frameworks-spring-db-migrations-flyway
• 314-frameworks-spring-kafka
• 315-frameworks-spring-mongodb
• 316-frameworks-spring-mongodb-migrations-mongock
• 321-frameworks-spring-boot-testing-unit-tests
• 322-frameworks-spring-boot-testing-integration-tests
• 323-frameworks-spring-boot-testing-acceptance-tests
• 400-frameworks-quarkus-create-project
• 401-frameworks-quarkus-core
• 402-frameworks-quarkus-rest
• 403-frameworks-quarkus-validation
• 404-frameworks-quarkus-security
• 411-frameworks-quarkus-jdbc
• 412-frameworks-quarkus-panache
• 413-frameworks-quarkus-db-migrations-flyway
• 414-frameworks-quarkus-kafka
• 415-frameworks-quarkus-mongodb
• 416-frameworks-quarkus-mongodb-migrations-mongock
• 421-frameworks-quarkus-testing-unit-tests
• 422-frameworks-quarkus-testing-integration-tests
• 423-frameworks-quarkus-testing-acceptance-tests
• 500-frameworks-micronaut-create-project
• 501-frameworks-micronaut-core
• 502-frameworks-micronaut-rest
• 503-frameworks-micronaut-validation
• 504-frameworks-micronaut-security
• 511-frameworks-micronaut-jdbc
• 512-frameworks-micronaut-data
• 513-frameworks-micronaut-db-migrations-flyway
• 514-frameworks-micronaut-kafka
• 515-frameworks-micronaut-mongodb
• 516-frameworks-micronaut-mongodb-migrations-mongock
• 521-frameworks-micronaut-testing-unit-tests
• 522-frameworks-micronaut-testing-integration-tests
• 523-frameworks-micronaut-testing-acceptance-tests
• 701-technologies-openapi
• 702-technologies-wiremock
• 703-technologies-fuzzing-testing
• 704-technologies-sql
• 705-technologies-nosql-mongodb
• 706-technologies-containers-docker
• 707-technologies-hexagonal-architecture
• 801-regulations-eu-ai-act
• 802-regulations-dora
• 803-regulations-gdpr
• 804-regulations-eu-nis2
• 805-regulations-eu-cyber-resilience-act
• 806-regulations-eu-data-act
• 807-regulations-eu-digital-services-act
• 808-regulations-eu-digital-markets-act
• 810-regulations-eu-mifid-ii
• 811-regulations-eu-market-abuse-regulation
• 812-regulations-eu-product-liability-directive
• 813-regulations-iso-42001
• 814-regulations-iso-25010
• openspec-propose
• openspec-propose