ce-work-beta

Execute plan documents and prompts via local implementation and Codex delegation.

14|3|Updated May 7, 2026
One-click install
npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill ce-work-beta-ouro-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-work-beta
Source: https://github.com/Ouro-labs/ouroboros-plugins/tree/main/plugins/compound-engineering/assets/skills/ce-work-beta
Command: npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill ce-work-beta-ouro-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the execution of work documents by providing experimental Codex delegation for token-conserving code implementation, streamlining systematic work execution and maintaining quality.

Core Features & Use Cases

  • Work Execution: Execute plan documents or bare prompts systematically to complete features.
  • Codex Delegation: Leverage Codex to handle code implementation for token conservation.
  • Use Case: When you have a work document describing a task, use this Skill to execute it, with the option to delegate code implementation to Codex for efficiency.

Quick Start

Run the ce-work-beta skill with a work document or prompt: ce-work-beta path/to/workdoc.md or ce-work-beta "description of the work".

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 from a plan document?

You can automate code implementation from plan documents by running ce-work-beta with your work file. It reads the Goals, Files, Approach, and Test scenarios sections to systematically execute and ship complete features.

What is Codex delegation for code implementation?

Codex delegation for code implementation is a process where work execution is offloaded to Codex to conserve tokens. This approach streamlines systematic work execution by leveraging external delegate support to handle code implementation tasks efficiently.

Do I need Codex to run the ce-work-beta Skill?

Yes, you need Codex available in your environment because it is listed as a required dependency. The Skill uses Codex delegation specifically for token-conserving code implementation during systematic work execution.

How do I execute a work document with goals and test scenarios?

To execute a work document, run the Skill command followed by your file path. The document must include Goals, Files, Approach, and Test scenarios to successfully automate the work execution and feature completion.

Can I run work execution using just a bare prompt instead of a full document?

Yes, you can run work execution using a bare prompt by passing a text description directly to the Skill. This allows you to handle feature completion without needing a structured plan document.

Are there limitations to using Codex delegation for work execution?

This is a Beta feature, meaning experimental Codex delegation for token-conserving code implementation may have limitations. It is designed for systematic execution of complete features but should be monitored for quality during the automation process.