JoinedWorkz skills and Codex plugin
JoinedWorkz skills are optional, reusable workflows for AI-assisted development. They help an agent follow JoinedWorkz release, modeling, verification, and generated-output rules for a bounded task. They do not replace the matching JoinedWorkz documentation, project context, or inspection of the current sources.
The skills are distributed together in the joinedworkz Codex plugin from the public JoinedWorkz skills repository. The plugin is also a convenient package for keeping both workflows on one tested, immutable release.
Exact compatibility for this documentation
This documentation mount describes JoinedWorkz 1.3.81. Plugin 0.1.0-beta.2 bundles exact verified profiles for JoinedWorkz 1.3.81.
JoinedWorkz 1.3.80 is only the candidate release floor of the workflows; it is not a compatibility or support claim and is currently unverified. The skills do not fall back to the nearest or latest profile. Mixed JoinedWorkz versions, prereleases, and SNAPSHOTs are not accepted release baselines.
What the plugin contains
| Skill | Use it for | Important boundary |
|---|---|---|
joinedworkz-create-application | Create and verify a new Spring Boot application, optionally with an experimental Quasar frontend, from a released Maven Archetype. | It stops for an existing target directory and never overwrites, merges, cleans, or deletes a project automatically. |
joinedworkz-openapi-to-cmn | Inventory an OpenAPI contract and convert representable OpenAPI 3.0.x semantics into authoritative CMN. | It reports ambiguous, lossy, and unsupported mappings instead of inventing persistence, components, applications, or runtime behavior. |
The OpenAPI skill can inventory OpenAPI 3.1 contracts, but it does not write CMN until any JSON Schema 2020-12 semantics have a documented and approved OpenAPI 3.0-compatible normalization.
Install the public beta in Codex
Use a Codex installation that provides the codex plugin commands. Register the public Git repository as a marketplace at the immutable beta tag, then install the joinedworkz plugin from the joinedworkz marketplace:
codex plugin marketplace add https://gitlab.com/joinedworkz/joinedworkz-skills.git --ref v0.1.0-beta.2
codex plugin add joinedworkz@joinedworkzPinning the tag makes the installed workflow reproducible. Do not replace it with the repository default branch for a release-based project.
Inspect the configured marketplace and installed plugin without changing a project:
codex plugin marketplace list
codex plugin list --marketplace joinedworkzStart a new top-level Codex task after installation so the bundled skills are loaded. You can then invoke a workflow explicitly when deterministic routing is useful.
Create and verify an application
Example prompt:
Use $joinedworkz-create-application to create and verify a new Spring Boot
application with H2. Show me the resolved parameters and target directory
before generation.For the verified JoinedWorkz 1.3.81 profile, application creation uses Maven Archetypes 1.0.0 and Maven Archetype Plugin 3.4.1. It requires Java 21 or newer, Maven 3.9 or newer for the initial generation, and access to the released Maven artifacts. H2 is the zero-Docker evaluation choice. Maven generation does not require JoinedWorkz Studio or a Studio license.
The skill builds the generated reactor sequentially with its Maven Wrapper:
./mvnw clean verifyIt never adds Maven -T, because model generation can write into downstream sibling modules. It also preserves authoritative CMN, manual application shells, and accepted Flyway migrations and schema snapshots according to their different ownership classes.
Convert OpenAPI into CMN
Example prompt:
Use $joinedworkz-openapi-to-cmn to inventory api/openapi.yaml, convert the
representable OpenAPI 3.0 contract into JoinedWorkz 1.3.81 CMN, and produce a
conversion report for every ambiguous, lossy, or unsupported construct.The skill preserves the source OpenAPI contract. It inventories schemas, references, paths, operations, parameters, bodies, responses, media types, security, callbacks, links, and extensions before writing CMN. JSON inventory uses the Python standard library; YAML inventory additionally requires PyYAML.
Generation success alone does not prove equivalence. The workflow parses, links, validates, and regenerates through the project build, then compares the resulting OpenAPI contract semantically with the source. It changes authoritative CMN or reports a limitation; it never repairs replaceable generated OpenAPI by hand.
Ownership and decision boundaries
Both skills follow the normal JoinedWorkz ownership rules:
- edit authoritative CMN, configuration, and manual project sources only;
- regenerate replaceable output instead of patching it;
- preserve first-cut sources and versioned generated history;
- keep Quasar explicitly experimental;
- stop when an exact verified release profile is unavailable;
- report a required product, architecture, compatibility, or contract decision instead of guessing.
An installed skill supplies a workflow, not additional repository, network, runtime, Docker, or data-mutation authority. The normal task scope and approval boundaries still apply.
Other Agent Skills clients
The canonical skill directories follow the Agent Skills directory convention. Tools that support individual Agent Skills but not Codex plugins can install a complete skill directory from the tagged repository. Tool-specific locations and reload behavior differ; use the repository installation guide and do not copy only selected files from a skill.
The Git-backed marketplace is a public distribution source for this plugin. It does not automatically list the plugin in the universal public plugin directory. See the official Codex plugin packaging documentation for that distinction and the current marketplace model.