Menu
Implement a piece of work based on a PRD or set of issues.
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
Build a domain-first KlumAST Schema. Use when a Domain API Developer and Schema Developer want to model a domain independently of downstream targets, decide between Layer 3 and direct-schema, define DSL Object boundaries, and prove the resulting completed model with an API-only client and executable test.
Build a KlumAST authoring Schema for an authoritative external contract. Use when an adopter is replacing or simplifying Helm values, another configuration document, or a target-specific API contract while keeping that contract authoritative.
Advise on applicable KlumAST features in an existing Schema or configured model. Use when an adopter wants a ranked, evidence-based KlumAST improvement review, an explanation of supported 4.x features that fit their model, or selected, validated model improvements.
Author a configured KlumAST model. Use when a Model Writer wants to turn a representative configuration into a KlumAST model, add validation, construct it through the generated DSL, or create an executable model test.
Start or adapt a Gradle project for KlumAST. Use when an adopter wants to scaffold a KlumAST project, add KlumAST to an existing Gradle build, choose domain-first or target-contract modeling, choose Layer 3 or direct-schema structure, or verify a first schema build.
Maintain a compact, evidence-backed horizon of user-selectable repository work; create and reconcile user-visible tasks without confusing completed execution with delivered repository state.
| name | implement |
| description | Implement a piece of work based on a PRD or set of issues. |
Implement the work described by the user in the PRD or issues.
Read the repository's agent instructions, docs/agents/coding-style.md, docs/agents/commits.md, and docs/agents/pull-requests.md. Before the first commit, create a new branch dedicated to the issue from the agreed base, or confirm the current branch was newly created for this issue.
Use /tdd where possible, at pre-agreed seams. Commit each completed reasoning slice according to docs/agents/commits.md; a TDD commit contains the failing test and the change that makes it green.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Keep required documentation consistent with the final behavior. It may be a separate final commit.
Once done, use /code-review against the issue branch base, commit any fixes, then review and improve the complete commit sequence as required by docs/agents/commits.md before first publication. Re-run the final verification after any history rewrite. When responding to pull-request review feedback, preserve the reviewed commits, add one or more focused follow-up commits, push them, and post the consolidated disposition required by docs/agents/pull-requests.md.
