ce-work

Coordinate phase-driven work execution from plan to delivery.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-work-bradliebs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-work
Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.github/skills/ce-work
Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-work-bradliebs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end work execution from plan to delivery, ensuring quality and feature completeness across teams.

Core Features & Use Cases

  • Phase-driven execution: input triage, plan reading, task creation, execution, testing, review, and post-deploy monitoring.
  • Plan-centered task orchestration: derives tasks from a work plan and tracks progress with execution notes and verification criteria.
  • Continuous quality and iteration: runs tests after changes, performs incremental commits, and enforces code reviews per project standards.

Quick Start

Provide a work plan document and this skill will orchestrate execution from planning to delivery.

Frequently Asked Questions about ce-work

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

FAQPage Schema
How do I coordinate end-to-end work execution from planning to delivery?

End-to-end work execution is coordinated through a phase-driven workflow that triages inputs, reads plans, creates tasks, executes changes, discovers tests, performs incremental commits, and validates final features. This ensures complete features are shipped with continuous quality checks.

What is phase-driven development workflow for shipping features?

Phase-driven development workflow is a structured process moving through input triage, plan reading, task creation, execution, test discovery, incremental commits, and final validation. It ensures feature completeness and quality by enforcing verification criteria and code reviews at each stage.

How to automate task creation from a software development plan?

Automating task creation from a development plan involves plan-centered task orchestration. The process derives actionable tasks from a provided work plan document and tracks progress using execution notes and verification criteria throughout the development lifecycle.

Does this work execution skill support both frontend and backend tasks?

Yes, this work execution skill explicitly supports both frontend and backend tasks. It applies to projects containing implementation units, test scenarios, and reviewer steps, maintaining a consistent phase-driven workflow across the entire technical stack.

When do I need a plan-centered task orchestration workflow?

You need plan-centered task orchestration when coordinating complex projects from plan to delivery. It is essential when your project requires deriving tasks from a work plan, enforcing code reviews, running tests after changes, and performing incremental commits to maintain quality.

What's the best way to ensure code review and testing during feature development?

The best way to ensure code review and testing is using a continuous quality and iteration process. This approach runs tests after changes, performs incremental commits, and enforces code reviews per project standards throughout the execution phase.