Nova Produce Plan

Shared Execution Policy

This file is the supporting behavioral contract for /nova-plugin:produce-plan and the deprecated /nova-plugin:nova-produce-plan compatibility entrypoint. Prefer the direct command; the compatibility name remains only for the current major-version migration window.

• Resolve natural-language and explicit KEY=value inputs using ../_shared/parameter-resolution.md; explicit non-conflicting values take precedence.
• Apply ../_shared/safety-preflight.md before side effects. Never infer approval, destructive scope, credentials, or output destinations.
• Follow ../_shared/output-contracts.md and ../_shared/artifact-policy.md; report completed, skipped, and blocked validation truthfully.
• Respect the frontmatter tool boundary. Missing inputs, unavailable dependencies, overlapping user changes, or repository-policy conflicts are blockers rather than permission to broaden scope.

Execution

1. Parse $ARGUMENTS against the workflow-specific inputs below.
2. Read only the context required for the requested scope.
3. Apply the workflow contract and its strict output format.
4. Stop before unauthorized side effects; otherwise validate in proportion to risk and report residual risk.

Workflow Contract

Generated from workflow-specs/behaviors.v2.json. This block is authoritative. Run node scripts/generate-behavior-surfaces.mjs --write after changing the IR; if explanatory text below conflicts, fail closed.

Generated Behavior Index

• Purpose: Write a review-ready plan artifact from explicit intent and constraints without implementing code.
• Canonical inputs: REQUEST(required aliases=PLAN_INTENT,INPUT); PLAN_OUTPUT_PATH(required aliases=OUTPUT_PATH); PLAN_PROFILE(optional aliases=PROFILE default="general" exact="general","lite","java-backend"); ANALYSIS_INPUTS(optional aliases=EVIDENCE); CONSTRAINTS(optional aliases=BOUNDARIES)
• Resolved variant authority: {"PLAN_PROFILE":"java-backend"} normalized={"PLAN_PROFILE":"java-backend"} -> runtime/contracts/backend-plan.json; {"PLAN_PROFILE":"lite"} normalized={"PLAN_PROFILE":"lite"} -> runtime/contracts/plan-lite.json; {} normalized={"PLAN_PROFILE":"general"} -> runtime/contracts/produce-plan.json. Declared selector defaults are applied before matching. An exact normalized override wins; a non-exact combination that triggers an alias specialization stops as conflicting, and only a valid combination that triggers no specialization uses the canonical fallback. The complete resolved runtime contract is authoritative and no field falls back to canonical prose.
• Claude static-entrypoint gate: Native command and Skill frontmatter are static. A matching command wrapper may continue after it has verified that its invoked command id equals resolvedWorkflowId; this canonical Skill must not re-resolve or reject that validated wrapper. Only when this canonical Skill is itself the Claude native invoked entrypoint and no validated wrapper gate exists must resolvedWorkflowId equal produce-plan. Otherwise STOP before tools or side effects and invoke the exact direct command /nova-plugin:<resolved commandEntrypoint.directCommandId>; never execute the specialized contract under unmatched canonical frontmatter. Generic and Codex adapters may execute the resolved contract directly under adapter enforcement.
• Decision entries: 2; canonical routes and variants: produce-plan {"PLAN_PROFILE":"java-backend"}.
• Workflow steps: validate-inputs → load-evidence → select-profile → write-plan → summarize
• Output: mode=artifact; order=plan artifact → artifact path → executive summary; severity=none.
• Deviation/failure: mode=approval-required; failure order=status → blocker → required input → safe next action.
• Full IR: runtime/contracts/produce-plan.json#behaviorContract embeds the complete decision table, invariants, stops, field definitions, validation, and failure contract from the same source. Detailed guidance below may not override it.

Purpose

Generate review-ready design/plan documentation based on intent and constraints.

Inputs

Outputs

• general and java-backend write a full plan document to the explicit path and return only that path plus executive-summary bullets in chat.
• lite uses the resolved plan-lite chat-only contract and does not require or infer PLAN_OUTPUT_PATH.

Workflow

1. Validate required fields.
2. Select profile template.
3. Produce complete plan with explicit trade-offs.
4. For artifact profiles, write the file and return the constrained chat summary; for lite, emit only the resolved chat outline.

Examples

• Natural trigger: Use produce-plan to draft a formal plan for payment retry flow.
• Explicit trigger: produce-plan PLAN_OUTPUT_PATH=docs/plans/auth.md PLAN_INTENT=Unify auth chain PLAN_PROFILE=general.

Safety

• Design only, no code change.
• Stop when required fields are missing.

Profile Document Structure

For general and java-backend, write a review-ready design checkpoint only to the explicit PLAN_OUTPUT_PATH; never infer it. Base decisions on supplied evidence and constraints, keep alternatives and trade-offs explicit, and do not modify production code. lite follows its resolved chat-only runtime contract.

Profile: general (default)

The plan document MUST include these 9 sections in order:

1. Background & Problem Statement

   • Context leading to this plan
   • Summary of the problem being addressed
   • Pointers to relevant analysis artifacts

2. Goals & Non-Goals

   • Explicit success criteria
   • Clearly stated non-goals to prevent scope creep

3. Constraints & Assumptions

   • Technical, organizational, or temporal constraints
   • Assumptions inherited from analysis or business context

4. Alternatives Considered

   • Meaningful alternatives that were evaluated
   • High-level pros and cons of each
   • Clear reasons for rejection

5. Final Approach & Rationale

   • Chosen approach
   • Why this approach best satisfies goals and constraints
   • Key trade-offs being accepted

6. Step-by-Step Implementation Plan

   • Ordered implementation phases
   • Key milestones or checkpoints
   • Ownership or responsibility boundaries if relevant

7. Risks & Mitigations

   • Technical, operational, and delivery risks
   • Concrete mitigation strategies (not just acknowledgements)

8. Test & Validation Strategy

   • How correctness will be validated
   • Types of tests required (unit, integration, manual, etc.)
   • Rollout validation signals

9. Rollback Strategy

   • Conditions under which rollback is required
   • High-level rollback steps
   • Expected impact and limitations

Profile: java-backend

For Java/Spring backend designs, include these 12 sections:

1. Background & Problem Statement
2. Scope Definition (what is in/out of scope)
3. Business Rules & Invariants (domain constraints, validation rules)
4. Architecture Overview (layers, modules, boundaries)
5. Data Model & Persistence (entities, repositories, schema considerations)
6. Transaction & Consistency Design (transaction boundaries, isolation levels, distributed transactions)
7. Concurrency & Idempotency (thread-safety, race conditions, retry handling)
8. Error Handling & Observability (exception strategy, logging, metrics, tracing)
9. Implementation Plan (Step-by-Step)
10. Testing Strategy (unit, integration, contract tests)
11. Rollback & Safety Plan
12. Risks & Open Questions

OUTPUT RULES

Chat output MUST include ONLY:

1. The absolute or relative file path written
2. A 3–5 bullet executive summary:
   • What is being done
   • Why this approach was chosen
   • Major risks or trade-offs

Do NOT:

• Paste the plan content into chat
• Add commentary outside the required output

4.0 VARIANT PROFILES

• Default: formal review-ready plan written to PLAN_OUTPUT_PATH.
• PLAN_PROFILE=lite: former plan-lite chat-only behavior; no artifact path is inferred.
• PLAN_PROFILE=java-backend: former backend-plan twelve-section Java/Spring profile.

The former plan-review entry is a nova-review variant, not a planning writer.

END OF COMMAND