ce-work-beta

Plan and execute work batches with optional Codex delegation.

10|Updated Dec 13, 2016
One-click install
npx skills add https://github.com/vitallium/dotfiles --skill ce-work-beta-vitallium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-work-beta
Source: https://github.com/vitallium/dotfiles/tree/main/dot_agents/skills/ce-work-beta
Command: npx skills add https://github.com/vitallium/dotfiles --skill ce-work-beta-vitallium

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

## What problem does it solve? ce-work-beta addresses the complexity of coordinating work that may be delegated to Codex in order to accelerate delivery while preserving planning, review, and auditability within the existing ce-work framework.

## Core Features & Use Cases

  • Beta Codex delegation mode enables token-conscious code implementation alongside the stable ce-work workflow.
  • Supports planning, batching, delegation checks, and deterministic execution with per-batch effort control.
  • Use cases include large feature work that benefits from isolated execution units and optional external delegation without sacrificing safety or traceability.

### Quick Start Provide a plan file path and/or a plain description of work to trigger a delegated batch run with the ce-work-beta workflow.

Frequently Asked Questions about ce-work-beta

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

FAQPage Schema
How do I delegate batch coding tasks to Codex while preserving standard git workflows?▼

Codex delegation batches code implementation units by routing planned work through per-batch effort gating, preserving standard ce-work behavior and auditability when delegation is inactive.

What is the best way to plan and batch large feature work for deterministic execution?▼

Batch large feature work by providing a plan file path or plain description to trigger isolated execution units with deterministic per-batch effort control for safe, auditable shipping.

Can I use ce-work-beta for token-conscious code implementation without losing planning review?▼

Yes, ce-work-beta enables token-conscious code implementation alongside planning, batching, and delegation checks, ensuring safe and traceable delivery within the existing workflow.

Does ce-work-beta require a plan file path to trigger a delegated batch run?▼

No, you can trigger a delegated batch run by providing either a plan file path or a plain text description of the work to execute with the ce-work-beta workflow.

Why does standard ce-work behavior still run when Codex delegation is not active?▼

Standard behavior runs because config gating ensures deterministic execution only delegates to Codex when active, preserving safe and auditable planning workflows otherwise.

When should I not use Codex delegation for isolated execution units?▼

Avoid delegation when work lacks clear plan file boundaries or per-batch effort definitions, as config gating requires isolated execution units to ensure safe, auditable shipping.