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.

Workflow implementation stage used only after plan.md is ready-for-implementation. This stage owns plan.md -> backend implementation -> review-ready handoff inside the six-stage workflow; it may invoke the Java implementation helper only when the current message still allows implementation, and it is not itself a direct fallback helper.

Use only after feasibility.md is ready-for-plan. This stage reads requirement.md and feasibility.md, writes plan.md, and may unlock implementation only through gate: ready-for-implementation.

Workflow fifth-stage self-review used after backend implementation reaches review-ready handoff and before any plugin work. This stage owns review-and-fix, self-review.md, and the gate/next decision for plugin unlock or upstream recovery; it may invoke the Java review helper when needed, but it is not itself a direct fallback helper.

Package-level first entry for fresh, uncertain, or continuing requests in the backend Java web workflow. Start here to interpret raw requests, prioritize explicit requirement-first or no-implementation intent over 'start/continue' wording and technical detail, reopen an existing task, or route to the only legal stage or explicit direct fallback.