gh:work-beta

Delegate implementation tasks to Codex within Gale Harness CLI batch workflows.

2|1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-work-beta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh:work-beta
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/gh-work-beta
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-work-beta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

gh-work-beta enables efficient work execution by delegating implementation tasks to Codex while preserving overall workflow planning and governance.

Core Features & Use Cases

  • Codex delegation (beta) offloads concrete coding tasks to Codex while you maintain control over planning and reviews.
  • Batch-enabled execution with guardrails supports multi-unit plans, environment checks, consent flows, and result verification to ensure safe delegation.
  • Trial scenarios compare delegated vs local implementation within Gale Harness CLI workflows for risk management and iteration.

Quick Start

Provide a work plan to begin Phase 1 and enable Codex delegation to trial the beta workflow.

Frequently Asked Questions about gh:work-beta

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate work execution by delegating coding tasks to Codex?

Codex delegation automates work execution by offloading implementation tasks while preserving overall planning and governance. You provide a work plan, and the system manages batching, environment checks, consent handling, and post-execution verification.

How does batch-enabled execution with guardrails handle multi-unit plans?

Batch-enabled execution manages multi-unit plans by applying environment checks, consent flows, and result verification. This ensures safe delegation by validating each batch before execution and verifying outcomes against the provided work plan.

Can I compare delegated implementation against local execution within CLI workflows?

Trial scenarios compare delegated Codex implementation against local execution within CLI workflows. This supports risk management and iteration by evaluating the safety and effectiveness of delegating concrete coding tasks.

Do I need to provide a work plan to start using Codex delegation?

Providing a work plan is required to begin Phase 1 and enable Codex delegation. The plan initiates the beta workflow, allowing the system to parse requirements, gate delegation, manage batches, and report execution results.

What are the limitations of using beta Codex delegation for workflow automation?

Beta Codex delegation is limited to batch work units within CLI workflows and requires explicit consent handling. Users must manage orchestration control manually and rely on post-execution verification to ensure delegated tasks meet plan requirements.

Why does workflow delegation require environment checks and consent handling?

Environment checks and consent handling are required to gate delegation and ensure safe execution. These guardrails validate the environment before processing batch work units, preventing unverified or unauthorized implementation tasks from running.