governed-workflowlisted

# Governed Workflow Skill Multi-phase implementation workflow with backend-enforced transitions. Every phase advance is validated server-side — the orchestrator cannot self-certify readiness. **Start every session by calling `workspace_get_state`.** The `phase` field tells you where you are. The `previous_sessions` field tells you whether this is a fresh start or a continuation. --- ## Agent Roles: All Agents Are Resumable Sub-agents All agents — including plan-advisor — are resumable sub-agents. Spawn with `Agent(name: "...", ...)` and continue via `SendMessage(to: "name", ...)`. ``` Agent( name: "plan-advisor", subagent_type: "plan-advisor", run_in_background: true, prompt: "..." ) ``` ``` Agent( name: "researcher-auth", subagent_type: "code-researcher", prompt: "..." ) ``` Agents execute their task and return. The orchestrator continues them for follow-up via `SendMessage(to: "<name>")`. **Plan-advisor** is spawned once in Phase 0 with `run_in_background: true` and continued throughout the session via `SendMessage(to: "plan-advisor", ...)`. All other agents are spawned per-task and may be continued if needed. ### Spawn rules per role | Role | When | |------|------| | **plan-advisor** | Phase 0 (background), messaged in phases 1.0, 1.3, 2.0, 3.N.0 | | senior-backend-engineer | Complex sub-phases spanning 3.N.0 → 3.N.2 fix cycles. Continue via SendMessage. Production code ONLY — never tests. | | senior-backend-test-engineer | Complex test scenarios s