ce-work-beta

Execute code implementation tasks via Codex delegation with parallel execution.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-work-beta-zeptiny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-work-beta
Source: https://github.com/Zeptiny/opencode-setup/tree/main/skills/ce-work-beta
Command: npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-work-beta-zeptiny

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codex, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The ce-work-beta Skill streamlines the execution of work, enabling users to systematically implement features with experimental Codex delegation, which conserves tokens and maintains quality.

Core Features & Use Cases

  • Codex Delegation: Utilizes Codex for token-conserving code implementation, with options for full-auto or yolo sandbox modes.
  • Task Execution Loop: Executes tasks based on plan documents or prompts, with support for inline and serial/subagent execution strategies.
  • Quality Check and Finishing Work: Ensures code quality through continuous testing, simplification, and Figma design sync when applicable.
  • Parallel Execution: Allows for parallel subagent execution, with safety checks to prevent file collisions and worktree isolation to ensure subagent isolation.
  • Incremental Commits: Promotes clean commit practices by evaluating tasks for commit readiness and guiding commit messages.
  • Test-Driven Development: Encourages test-first and characterization-first approaches to development, with support for test discovery and completeness checks.

Quick Start

Run the ce-work-beta skill with a plan document or description of work. Example: skill ce-work-beta my-plan.md

Frequently Asked Questions about ce-work-beta

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

FAQPage Schema
How do I automate code implementation tasks using Codex delegation?

Automating code implementation with Codex delegation requires a plan document or prompt input. The system executes tasks through an automated loop, utilizing serial or parallel subagent strategies to write and validate code efficiently.

What is the best way to run parallel task execution for complex codebases without file collisions?

Parallel task execution for complex codebases prevents file collisions by using safety checks and worktree isolation. This ensures subagent isolation, allowing multiple implementation tasks to execute simultaneously without overwriting shared files.

Can I use test-driven development with automated task execution loops?

Test-driven development is supported within the task execution loop. The system encourages a test-first and characterization-first approach, automatically discovering tests and checking completeness to validate code quality during implementation.

Does Codex delegation support incremental commits for large feature development?

Incremental commits are supported during large feature development. The system evaluates tasks for commit readiness and guides commit messages, promoting clean commit practices throughout the software development workflow.

How do quality checks and finishing work function during automated code writing?

Quality checks during automated code writing ensure continuous testing and code simplification. The finishing work phase also includes Figma design sync when applicable, verifying that the implementation meets design and functional requirements.

Do I need specific configuration settings to use Codex for token-conserving code generation?

Specific configuration settings are required to use Codex for token-conserving code generation. Users must configure the Codex model and effort level, with options for full-auto or yolo sandbox modes to control the execution environment.