sprint-deliver

name	sprint-deliver
description	Delivers the sprint by executing /deliver-use-case for each use case in priority order. Reads the delivery order from the sprint readiness report and starts with the first priority. Currently delivers one use case at a time — human in the loop is needed after each use case finalization. Will be extended in the future to deliver the full sprint autonomously.
user_invocable	true
arguments	none

Sprint Deliver

Instructions

Deliver the next use case from the sprint scope by invoking /deliver-use-case.

Nexa Rules Gate

Read and follow ${CLAUDE_PLUGIN_ROOT}/shared/readiness/NEXA_RULES_GATE.md.

Sprint Branch Gate

Read and follow ${CLAUDE_PLUGIN_ROOT}/shared/readiness/SPRINT_BRANCH_GATE.md.

Step 1: Locate the Sprint Folder

The active sprint is always docs/sprints/next-sprint/.

If docs/sprints/next-sprint/ does not exist, stop and tell the user to run /sprint-prepare first.

Step 2: Read and Validate the Readiness Report

Read docs/sprints/next-sprint/readiness-report.md.

If the readiness report does not exist, stop and tell the user to run /sprint-prepare first.

Check the Verdict

Find the ## Verdict line. If the verdict is BLOCKERS REMAIN, stop and display:

SPRINT NOT READY — blockers found in readiness report.

[paste the Gaps section from the readiness report]

Resolve these blockers and re-run /sprint-prepare, or address them manually
before running /sprint-deliver again.

Check Pre-Delivery Actions

Find the Pre-Delivery Actions table. For each action listed:

1. Prisma migration (/prisma-migration): Check if prisma/schema.prisma contains the entities listed in the readiness report's Entity Model Changes. If the changelog says "Migration Required: Yes" and the schema is missing expected models, stop and tell the user:

   PRE-DELIVERY ACTION REQUIRED: Run /prisma-migration before delivery.
   The entity model was updated during sprint preparation but the Prisma
   schema has not been migrated yet.
   

2. Other actions: Display them to the user and ask for confirmation that they have been completed before proceeding.

Check for Warnings

Find the Gaps section in the readiness report. If there are any warning-severity gaps (items that are not blockers but represent risks), display them to the user:

WARNINGS from sprint readiness report:

[paste each warning-severity gap with its Type, Affected UCs, and Description]

These warnings did not block sprint readiness but represent risks.
Proceed with delivery, or address them first and re-run /sprint-prepare?

Wait for the user to confirm before proceeding. If the user chooses to address the warnings, stop — they will re-run /sprint-prepare or fix the issues manually.

Read the Delivery Order

Find the Delivery Order table. This table lists use cases in recommended delivery sequence with columns: #, UC ID, Name, Rationale.

If there is no Delivery Order table, stop and tell the user to run /sprint-prepare first — the sprint is not ready for delivery.

Step 3: Identify the Next Undelivered Use Case

Walk the Delivery Order table from row # 1 downward. For each row, check whether docs/delivery/<UC ID>-iterations.md exists. If it does, that use case has already been delivered — skip it and move to the next row.

Select the first row whose UC has no iteration log as the next use case to deliver.

If all rows have been delivered, stop and report:

SPRINT COMPLETE — all use cases in the delivery order have been delivered.

Delivered:
- <UC ID> — <Name> (each row)

Next step: run /sprint-complete to close the sprint, update the dashboard,
and publish the report.

Otherwise, display the selected use case and the overall progress:

Sprint: next-sprint
Progress: <N delivered> / <total> use cases

Next: <UC ID> — <Name>
Rationale: <Rationale from table>

Previously delivered this sprint:
- <UC ID> — <Name> (for each already-delivered row, or "None" if first)

Step 4: Verify Spec and Design Exist

Before delivery, verify that /sprint-prepare produced the expected artifacts for the selected use case:

1. Check that docs/use_cases/<UC ID>.md exists.
2. Check that docs/designs/<UC ID>-design.html exists.

If either is missing, stop and tell the user:

MISSING ARTIFACTS for <UC ID>:

- Specification: [exists / MISSING]
- Frontend Design: [exists / MISSING]

These should have been generated by /sprint-prepare (Phase 6).
Re-run /sprint-prepare to generate them.

Step 5: Deliver the Use Case

Invoke /deliver-use-case <UC ID>.

Follow the full /deliver-use-case pipeline as defined in its SKILL.md — do not abbreviate or skip any steps.