ce:work

Execute plan-driven software engineering tasks with branching and testing discipline.

Updated Nov 11, 2023

Search Tags:#developer-workflow #feature-delivery #task-triage #plan-automation #work-execution #quality-maintenance

Ready to run

npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-work-michaelvolz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce:work
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/ce-work
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-work-michaelvolz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates uncertainty when executing work by guiding you from plan interpretation to quality delivery, ensuring features and fixes are completed reliably.

Core Features & Use Cases

Input triage: Decide whether a plan document is provided or a bare prompt describes the work, then adjust execution flow accordingly.
Execution discipline: Follow the prescribed control flow of plan review, environment setup, task breakdown, testing, review, and monitoring to maintain quality.
Use case: Ideal for developers tasked with shipping a defined feature, bug fix, or quality improvement with explicit expectations around branching, testing, and incremental commits.

Quick Start

Launch ce:work with your plan document path or a concise description so it can prepare the environment, create tasks, and run the workflow.

Frequently Asked Questions about ce:work

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

FAQPage Schema

How do I execute software development tasks from a plan document efficiently?▼

To execute work systematically from a plan document, provide the plan path or prompt description to trigger environment preparation, task breakdown, and incremental commits. The workflow enforces branching discipline, testing, and review preparation before marking tasks complete.

What is the best way to triage feature delivery tasks in a developer workflow?▼

Triage feature delivery tasks by evaluating whether a plan document or bare prompt describes the work, then adjusting the execution flow accordingly. This input triage ensures proper task breakdown and branching discipline before development begins.

Can I use a bare prompt to ship a bug fix without a formal plan document?▼

Yes, bare prompts can guide bug fixes without a formal plan document. Input triage identifies whether a plan document or prompt description defines the work, adjusting execution flow to maintain branching, testing, and review discipline.

Does plan automation require branching and testing discipline for quality improvements?▼

Yes, plan automation requires branching and testing discipline for quality improvements. The workflow enforces testing, incremental commits, and review preparation before marking tasks done, ensuring quality maintenance throughout feature delivery.

What are the limitations of automated work execution without explicit conventions?▼

Automated work execution without explicit conventions struggles to maintain quality focus. The workflow relies on existing conventions to guide plan reading, task triage, and review preparation, ensuring features and fixes are completed reliably.