Stats
Actions
Tags
From nova-plugin
Generate a Java/Spring backend design plan and write it to an explicit PLAN_OUTPUT_PATH.
How this command is triggered — by the user, by Claude, or both
Slash command
/nova-plugin:backend-planThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /backend-plan Invoke `nova-backend-plan` with `$ARGUMENTS`. This is the Java/Spring backend planning shortcut. The skill is the source of truth for parameter resolution, execution rules, output format, artifact policy, and safety boundaries. Entry semantics: - Equivalent in intent to `/produce-plan PLAN_PROFILE=java-backend`. - Requires explicit `PLAN_OUTPUT_PATH` before writing. - Keeps the legacy backend-focused slash entry available.
Invoke nova-backend-plan with $ARGUMENTS.
This is the Java/Spring backend planning shortcut. The skill is the source of truth for parameter resolution, execution rules, output format, artifact policy, and safety boundaries.
Entry semantics:
/produce-plan PLAN_PROFILE=java-backend.PLAN_OUTPUT_PATH before writing.npx claudepluginhub lliangcol/llm-plugins-fusion --plugin nova-plugin