GxFn
UserDual-host Wakeflow plugins for Codex and Claude Code: controller state roots, task packages, direct-thread/session delivery, evidence review, and local-first runtime.
Categories
Indexed Skills (16)
wakeflow-design
Use when a Wakeflow Design window needs to clarify a requirement, compare options, prepare or revise a requirement design, propose vertical work slices, or deliver a confirmed design to its controller.
wakeflow-test
Use when a Wakeflow Test window receives a controller-approved implementation-validation task or a controller-scoped Test-only reproduction or environment-diagnostic task and needs a bounded testing method.
design-handoff
Use in a Wakeflow Design window to prepare a compact handoff for controller intake from clarified requirements, option plans, requirement designs, and Design signals.
option-planning
Use in a Wakeflow Design window when a clarified requirement needs multiple implementation, architecture, sequencing, or rollout options before controller or user confirmation.
requirement-clarification
Use in a Wakeflow Design window when a user idea, controller request, handoff candidate, or product change needs clarification before it can become an original plan, requirement design, TODO candidate, or controller decision.
requirement-design
Use in a Wakeflow Design window to turn a clarified and confirmed requirement into a controller-intake-ready requirement design with user stories, decisions, tests, non-goals, and acceptance criteria.
work-slicing
Use in a Wakeflow Design window to break a confirmed requirement design into vertical-slice TODO or task-package candidates for controller intake.
debugging-and-triage
Use in a Wakeflow Test window when a test card, smoke run, runtime observation, or user report shows a failing or uncertain behavior that needs reproduction, root-cause tracing, and ownership classification.
evidence-review
Use in a Wakeflow Test window to review target evidence, diffs, reports, runtime logs, or validation output and return blockers, missing evidence, residual risk, and a controller-ready interpretation.
progressive-chain-validation
Use when the Test window needs a source-derived chain plan, node-by-node validation, isolated repair evidence, scoped round verdicts, before/after metrics, or a progressive validation plan for a long workflow.
regression-design
Use in a Wakeflow Test window to design behavior-focused regression coverage from a confirmed bug, requirement, test card, or target result without coupling to private implementation details.
test-strategy
Use in a Wakeflow Test window to design a risk-based validation plan for a controller test card, real-project scenario, release check, runtime observation, or cross-repository integration question.
wakeflow-target-craft
Use when a Wakeflow product target is about to implement or rework its assigned task package.
wakeflow-controller
Use when Wakeflow total control starts or resumes Wakeflow Delivery Loop, reviews strict TargetResult records, creates dispatch packets, builds delivery envelopes, decides acceptance / rework / block / next wave, or stops unattended automation.
wakeflow-governance
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.
wakeflow-target
Use when a target Codex window receives an exact Wakeflow v3 delivery, executes only its assigned TaskPackage, records a transport-bound TargetResult, or performs an authorized Controller return without taking controller authority.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.