From backend-java-web-development
Use only after self-review.md has gate: ready-for-plugin and the user explicitly confirms entering plugin work. This stage implements verification-support capability in apcp-plugin against a stable backend contract and may not redefine backend design.
How this skill is triggered — by the user, by Claude, or both
Slash command
/backend-java-web-development:apcp-plugin-implementationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This is the sixth stage of the workflow.
This is the sixth stage of the workflow. This stage is for plugin-side verification support only. It consumes a stable backend contract and must not redefine backend behavior.
Before starting, confirm all of the following:
tasks/<task-name>/requirement.md exists and has gate: requirement-confirmedtasks/<task-name>/feasibility.md exists and has gate: ready-for-plantasks/<task-name>/plan.md exists and has gate: ready-for-implementationtasks/<task-name>/self-review.md exists and has gate: ready-for-pluginself-review.md points to next: apcp-plugin-implementationapcp-web-api-self-review into this stageIf any check fails, refuse this stage and return to the only legal upstream stage.
This stage explicitly depends on self-review.md.
Without self-review.md and gate: ready-for-plugin, plugin implementation is forbidden.
Even with gate: ready-for-plugin, this stage is still forbidden until the user explicitly confirms entering plugin work.
If later backend changes invalidate the previous review result, plugin implementation stays forbidden until a fresh ready-for-plugin result is written again.
Do not treat backend implementation completion by itself as sufficient.
Do not treat plan.md by itself as sufficient.
apcp-plugin, use it as the plugin root.apcp-plugin from the parent directory of the current project.apcp-web-api and task documents from the same workspace when backend references are needed.Before coding, read:
requirement.mdfeasibility.mdplan.mdself-review.mdPlugin work must consume the stable backend contract only. It must not reopen backend requirement, feasibility, plan, implementation, or self-review decisions on its own.
Do not invoke any CodeLaw skill in this stage.
Strictly forbid the following in this stage:
If plugin work reveals that backend design is still unstable, stop and return to the stage named by the actual problem source.
If this skill is called directly without self-review.md being ready-for-plugin, refuse and point back to:
apcp-web-api-self-reviewself-review.mdIf the user has not explicitly confirmed entering plugin work yet, refuse and stay at the self-review-to-plugin confirmation boundary.
npx claudepluginhub kohlarnhin/backend-java-web-development --plugin backend-java-web-developmentGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.