ce:work

Execute plan documents into test-aware task lists with incremental commits.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill ce-work-xbpk3t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:work
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/ce-work
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill ce-work-xbpk3t

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns plan documents or brief prompts into an organized, test-aware execution plan and then carries out development work to complete and ship features while preserving quality, branch safety, and incremental commits.

Core Features & Use Cases

  • Plan ingestion & triage: Accepts plan files or bare prompts, classifies scope and routes execution (trivial, small/medium, large).
  • Execution orchestration: Builds task lists, manages branches or worktrees, supports inline and serial/parallel subagent strategies, and enforces test discovery and incremental commits.
  • Quality & shipping: Guides full quality checks, code review tiers, post-deploy monitoring, PR creation, and evidence capture for runnable changes.

Quick Start

Invoke the ce:work skill with a plan document path or a brief description of the work to start executing tasks and producing commits.

Frequently Asked Questions about ce:work

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

FAQPage Schema
How do I ship software features from a plan document with automated task management?

To ship software features from a plan document, this Skill ingests the plan, classifies scope, and orchestrates execution through task list creation, branch management, and incremental commits. It ensures test discovery and quality checks before guiding the final code review and deployment.

How does test discovery work during feature implementation?

Test discovery during feature implementation works by enforcing a test-first or characterization-first execution strategy. The Skill identifies relevant tests early in the workflow, runs them incrementally alongside code changes, and uses them to validate quality before creating a pull request or deploying.

Can I use git worktrees for parallel task execution and branch management?

Yes, you can use git worktrees for branch management. The Skill supports managing branches and worktrees to isolate development work. It applies serial or parallel subagent strategies to execute tasks safely without interfering with your main local environment.

What is the best way to manage small to medium-sized refactors and bug fixes?

The best way to manage small to medium-sized refactors and bug fixes is to route them through an automated execution plan that decomposes tasks, enforces test discovery, and manages git branches. This preserves branch safety and ensures incremental commits capture progress reliably.

Does this approach support code review and post-deploy monitoring?

Yes, this approach supports code review and post-deploy monitoring. The Skill guides full quality checks and tiered code reviews before shipping. After deployment, it captures evidence for runnable changes and facilitates post-deploy monitoring to ensure feature stability.

When should I avoid automated work execution for feature shipping?

You should avoid automated work execution if your project requires manual oversight for complex, large-scale architectural changes that exceed small to medium refactor scopes. The Skill classifies execution routing, but highly intricate tasks may need manual decomposition beyond its automated task list capabilities.