flow-develop

{{PREAMBLE}}

Pre-Development: State Check

Before starting development:

1. Read .octo/STATE.md to verify Define phase complete
2. Update STATE.md:
   • current_phase: 3
   • phase_position: "Development"
   • status: "in_progress"

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

# Update state for Development phase
"${HOME}/.claude-octopus/plugin/scripts/octo-state.sh" update_state \
  --phase 3 \
  --position "Development" \
  --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:

• Deliverable terms: "PRD", "proposal", "presentation", "report", "strategy document", "business case"
• Business terms: "market entry", "competitive analysis", "stakeholder", "executive summary"

Dev Context Indicators:

• Technical terms: "API", "endpoint", "function", "module", "service", "component"
• Action terms: "implement", "code", "build", "create", "develop" + technical noun

Also check: Does project have package.json, Cargo.toml, etc.? (suggests Dev Context)

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 quality guidance into the prompt sent to providers. Append the matching supplement text after the user's prompt.

Subtype	Trigger keywords	Quality supplement
frontend-ui	"page", "widget", "component", "UI", "HTML", "CSS", "form", "dashboard", "layout"	See frontend-ui enrichment below.
cli-tool	"CLI", "command-line", "terminal", "script", "flag", "argument"	Help text via --help flag. Meaningful exit codes (0 success, 1 user error, 2 system error). Stdin/stdout/stderr used correctly. Argument validation with clear error messages.
api-service	"API", "endpoint", "REST", "GraphQL", "gRPC", "server", "route"	Input validation at boundaries. Consistent error response format. Auth/authz on every endpoint. Rate limiting consideration. OpenAPI/schema documentation.
infra	"deploy", "terraform", "docker", "CI", "pipeline", "Kubernetes", "helm"	Idempotent operations. Secrets never hardcoded. Rollback path documented. Health checks included.
data	"ETL", "pipeline", "migration", "schema", "database", "SQL"	Idempotent migrations. Backup/rollback strategy. Data validation at ingestion.
general	Default if no subtype matches	No supplement — use base implementer persona only.