wakeflow-governancelisted

Use when working inside Wakeflow on workspace initialization / setup, AGENTS.md / skill layering, TODO / Backlog intake, Design handoff intake, idle-window scheduling, window coverage, task-package dispatch, producer/consumer sequencing, unified dispatch prompts, test handoffs, validation boundaries, or workspace script pipelines. This skill supplements AGENTS.md and must not override its hard boundaries.
GxFn/Wakeflow · ★ 5 · AI & Automation · score 77

Install: claude install-skill GxFn/Wakeflow

# Wakeflow Governance This skill holds detailed Wakeflow procedures that are too bulky to keep fully resident in `AGENTS.md`. ## Scope For workspace initialization or setup requests, use the Wakeflow MCP capability tool first: - Call `wakeflow_maintain_workspace` with `action: "fresh-initialize"`, `mode: "preview"`, and one closed `request.selection` for a fresh workspace. The selection explicitly partitions `program`, `topology`, `storage`, `governance`, and `hosts`; repository, support-surface, and window entries use request-local `selectionKey` links. Wakeflow allocates the durable typed IDs. - Preview is read-only. Review its blockers, exact `confirmedActionPlan`, returned `confirmedActionPlanDigest`, and `launchIntents`. Apply only after the user confirms the write boundary, by sending the same root and action with `mode: "apply"`, the exact confirmed plan, and that returned digest. - Use `action: "reconfigure"` only for an intentional desired-model change and `action: "reconcile"` only to restore managed bytes/projections from current v3 authority. Both follow the same preview-before-apply rule. `recover` requires the exact plan, digest, and incomplete mutation `operationId`. - Do not infer Design/Test from similar existing directory names such as `<WorkspaceName>Design`, `<ProductName>Design`, `<WorkspaceName>Test`, or `<ProductName>Test`. Unless the user explicitly names those as Design/Test, Wakeflow should create/use fresh `Design` and