Menu
Write a new Architectural Decision Record (ADR) for this project. Use when the user wants to document an architectural or design decision.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Write or refactor unit tests following the canonical project pattern. Use when adding new unit tests or standardizing existing ones.
Generate a Kotlin SingleModelValidationRule implementation for ONE rule from BPMN_STYLE_GUIDE.md. Use when drafting / iterating on a single rule, or when the user asks to 'generate a rule for <slug>', 'create the element-id-format rule', or 'add just this one rule to the test module'. For all rules at once, use generate-rules-to-enforce-bpmn-styleguide.
Generate Kotlin SingleModelValidationRule implementations for every deterministic (or hybrid) rule in BPMN_STYLE_GUIDE.md, so they can be enforced at test time by the bpmn-to-code-testing module. llm-only rules stay in the style guide for /validate-bpmn-style. Use when the user asks to 'generate validation rules from the style guide', 'enforce BPMN conventions in CI', or 'automate style checks in tests'. For a single rule, use generate-rule-to-enforce-bpmn-styleguide.
Interactively author a BPMN_STYLE_GUIDE.md for your project — a handbook that explains how the team models BPMN processes (naming, allowed elements, IDs, topics, engine-specific special cases). The output is a document humans can read; embedded YAML annotations let downstream skills enforce the rules. Use when the user asks to 'create a BPMN style guide', 'set up BPMN conventions', or 'define BPMN naming rules'.
Create a complete Spring Boot service project from a BPMN file with hexagonal architecture. Bootstraps via Spring Initializr, configures bpmn-to-code, and generates workers, use cases, and services wired to ProcessApi constants — no raw strings anywhere. Use when the user wants to start a new process service from a BPMN model.
Migrate generated API usage from bpmn-to-code v1.1.0 to v2.0.0. Use when the user asks to 'upgrade to v2', 'migrate from v1 to v2', 'fix TaskTypes references', or 'update bpmn-to-code API calls after upgrade'.
| name | create-adr |
| argument-hint | "<short description of the decision>" |
| allowed-tools | Read, Write, Glob |
| description | Write a new Architectural Decision Record (ADR) for this project. Use when the user wants to document an architectural or design decision. |
Write a new Architectural Decision Record following the format used in docs/contributing/adr/.
Use Glob to list all files matching docs/contributing/adr/*.md (excluding README.md).
Extract the three-digit numeric prefix from each filename (e.g. 011 from 011-variable-name-collision-detection.md).
The next number is the highest existing prefix plus one, zero-padded to three digits.
If no ADR files exist, start at 001.
Convert $ARGUMENTS to kebab-case: lowercase, replace spaces/underscores with hyphens, remove non-alphanumeric characters (except hyphens), collapse consecutive hyphens.
Target: docs/contributing/adr/{NNN}-{slug}.md
Read 1-2 recent ADRs to understand content style and level of detail:
docs/contributing/adr/011-variable-name-collision-detection.mddocs/contributing/adr/010-operaton-namespace-only-extractor.mdNote: Read these ONLY for writing style and technical detail level. Structure is defined in Step 5.
Ask the user (all at once, skip if $ARGUMENTS already answers):
Follow the structure from existing ADRs:
# ADR {NNN}: {Title}
## Status
Accepted
## Context
{Situation that motivated the decision}
## Decision
{What was decided and how it works}
### Implementation
{How this affects the codebase — new services, adapters, patterns}
## Consequences
### Positive
- {benefit}
### Negative
- {trade-off}
Add extra sections (e.g. ## Example, ## Alternatives Considered) only when they add meaningful value — follow the style of existing ADRs.
Show the complete draft to the user before writing.
Ask: "Write this ADR to {target-path}? (yes / edit / cancel)"
docs/contributing/adr/README.md by adding a link under the appropriate categoryOutput the created file path and remind the user to commit the ADR in the same commit as the related code change for traceability.