flow-deliver

{{PREAMBLE}}

Pre-Delivery: State Check

Before starting delivery:

1. Read .octo/STATE.md to verify Develop phase complete
2. Update STATE.md:
   • current_phase: 4
   • phase_position: "Delivery"
   • status: "in_progress"

# Verify Develop phase is complete
if [[ -f ".octo/STATE.md" ]]; then
  develop_status=$("${HOME}/.claude-octopus/plugin/scripts/octo-state.sh" get_phase_status 3)
  if [[ "$develop_status" != "complete" ]]; then
    echo "⚠️ Warning: Develop phase not marked complete. Consider completing development first."
  fi
fi

# Update state for Delivery phase
"${HOME}/.claude-octopus/plugin/scripts/octo-state.sh" update_state \
  --phase 4 \
  --position "Delivery" \
  --status "in_progress"

---

⚠️ EXECUTION CONTRACT (MANDATORY - CANNOT SKIP)

This skill uses ENFORCED execution mode. You MUST follow this exact sequence.

STEP 1: Detect Work Context (MANDATORY)

Analyze the user's prompt and project to determine context:

Knowledge Context Indicators:

• Document terms: "report", "presentation", "PRD", "proposal", "document", "brief"
• Quality terms: "argument", "evidence", "clarity", "completeness", "narrative"

Dev Context Indicators:

• Code terms: "code", "implementation", "API", "endpoint", "function", "module"
• Quality terms: "security", "performance", "tests", "coverage", "bugs"

Also check: What is being reviewed? Code files -> Dev, Documents -> Knowledge

Capture context_type = "Dev" or "Knowledge"

Step 1b: Detect Dev Subtype (if Dev context)

When context_type is Dev, determine the subtype to inject domain-appropriate validation criteria into the review prompt. Append the matching validation supplement after the user's prompt when calling orchestrate.sh in Step 4.

Subtype	Trigger keywords	Validation supplement
frontend-ui	"page", "widget", "component", "UI", "HTML", "CSS", "form", "dashboard", "layout"	Verify: all referenced files exist (scripts, stylesheets, images). Check ARIA labels and roles, keyboard navigability, touch target sizes (44px min). Flag innerHTML usage. Confirm progressive enhancement (fallbacks for navigator.share, localStorage, etc). Test self-containment: does this work if opened/run with zero setup?
cli-tool	"CLI", "command-line", "terminal", "script", "flag", "argument"	Verify: --help flag works, exit codes are meaningful (0/1/2), stderr vs stdout used correctly, argument edge cases handled (missing args, invalid input, --unknown-flag).
api-service	"API", "endpoint", "REST", "GraphQL", "gRPC", "server", "route"	Verify: input validation at every endpoint, consistent error response format, auth on protected routes, rate limiting considered, schema/contract documented.
infra	"deploy", "terraform", "docker", "CI", "pipeline", "Kubernetes", "helm"	Verify: operations are idempotent, no hardcoded secrets, rollback path exists, health checks included, destroy operations require confirmation.
data	"ETL", "pipeline", "migration", "schema", "database", "SQL"	Verify: migrations are reversible, data validation at ingestion, backup strategy documented, no data loss on failure.
general	Default if no subtype matches	No supplement — use standard review criteria.