ce:work-beta

Executes work plans or prompts with optional Codex delegation and phase-driven controls.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill ce-work-beta-andreicr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:work-beta
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/ce-work-beta
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill ce-work-beta-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Execute work efficiently by running a plan or bare prompt with optional Codex delegation, enabling faster delivery on feature work while maintaining governance.

Core Features & Use Cases

  • Beta Codex delegation: Try Codex-based delegation for batch execution of implementation units with controlled prompts and environment settings.
  • Plan-driven execution: Accepts a plan document or a bare prompt to drive phased Work Execution workflows with explicit delegation controls.
  • Guardrails & testing readiness: Enforces consent, sandbox modes, and structured execution phases including test discovery and incremental commits.

Quick Start

Provide a work plan file or a bare prompt to initiate the beta delegation workflow using ce:work-beta.

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 code implementation tasks to Codex for batch execution?

You can delegate code implementation tasks to Codex by providing a plan document or bare prompt, which the workflow parses to execute implementation units in controlled batches with configured environments.

What is phase-driven work execution and how does it manage incremental commits?

Phase-driven work execution is a structured workflow model that sequences tasks through explicit phases, enforcing test discovery and executing incremental commits to track progress throughout the implementation lifecycle.

Do I need a formal plan document to start a delegated execution workflow?

No, you do not need a formal plan document to start execution; the workflow accepts bare prompts directly, parsing them on the fly to initiate the delegation and planning process.

Can I configure sandbox modes and consent controls for delegated work?

Yes, you can configure sandbox modes and consent controls, as the workflow enforces strict delegation guardrails, sandbox consent, and environment configuration before executing any code.

What is the best way to execute feature work while maintaining governance controls?

The best way to execute feature work with governance is using plan-driven delegation, which applies structured execution phases, enforced consent, and sandbox modes to maintain control over automated delivery.

Why does test discovery matter in a delegated execution workflow?

Test discovery matters because the workflow integrates it directly into the execution phases, ensuring that incremental commits are validated against discovered tests before proceeding to the next implementation unit.