From nova-plugin
Generate a Java/Spring backend design plan with mandatory 12 sections and write to PLAN_OUTPUT_PATH.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nova-plugin:nova-backend-plan Example: backend-plan PLAN_OUTPUT_PATH=docs/plans/order-refund.mdExample: backend-plan PLAN_OUTPUT_PATH=docs/plans/order-refund.mdThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
| Parameter | Required | Default | Notes |
| Parameter | Required | Default | Notes |
|---|---|---|---|
PLAN_OUTPUT_PATH | Yes | None | Safety-boundary output file for the Java/Spring plan. |
PLAN_INTENT | Yes | Infer from payload | Business or technical goal for the backend plan. |
PLAN_PROFILE | No | java-backend | Fixed Java/Spring backend profile. |
ANALYSIS_INPUTS | Recommended | None | Prior exploration or analysis artifacts. |
CONSTRAINTS | No | None | Architecture, compatibility, delivery, or operational limits. |
KEY=value, --flag value, and --flag=value forms from $ARGUMENTS.PLAN_INTENT.PLAN_OUTPUT_PATH.nova-plugin/skills/_shared/parameter-resolution.md.Write, Edit.nova-plugin/skills/_shared/safety-preflight.md.nova-plugin/skills/_shared/output-contracts.md.nova-plugin/skills/_shared/artifact-policy.md./backend-plan as a Java/Spring profile shortcut for /produce-plan.KEY=value or --flag value; natural-language payload is accepted when unambiguous.Produce a complete Java/Spring backend design artifact for senior review.
| Parameter | Required | Default | Notes | Example |
|---|---|---|---|---|
PLAN_OUTPUT_PATH | Yes | N/A | Required output path | docs/plans/payment-callback.md |
| Business context | Recommended | N/A | Problem, goals, constraints | Duplicate callback handling |
Use backend-plan for this Java/Spring order refund flow.backend-plan PLAN_OUTPUT_PATH=docs/plans/refund-v2.md.Migrated from the pre-thin slash command contract for /backend-plan (nova-plugin/commands/backend-plan.md).
TASK: PRODUCE A JAVA / SPRING BACKEND DESIGN PLAN
You are Claude Code acting as a senior Java backend engineer / system designer.
Think carefully. Design decisions here will directly guide implementation.
From $ARGUMENTS, extract:
PLAN_OUTPUT_PATH: $PLAN_OUTPUT_PATH
If PLAN_OUTPUT_PATH is missing:
You MUST NOT guess or invent a path.
You MUST:
1️⃣ Background & Problem Statement 2️⃣ Scope Definition 3️⃣ Business Rules & Invariants 4️⃣ Architecture Overview 5️⃣ Data Model & Persistence 6️⃣ Transaction & Consistency Design 7️⃣ Concurrency & Idempotency 8️⃣ Error Handling & Observability 9️⃣ Implementation Plan (Step-by-Step) 🔟 Testing Strategy 1️⃣1️⃣ Rollback & Safety Plan 1️⃣2️⃣ Risks & Open Questions
Each section MUST be explicitly present. Use "N/A" if a section truly does not apply.
The plan MUST be:
If multiple design options exist:
You MUST:
In chat output ONLY:
You MUST NOT:
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub lliangcol/llm-plugins-fusion --plugin nova-plugin