ce:work

Automate plan-driven work execution with testing and incremental commits.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/sommio/RSSift --skill ce-work-sommio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:work
Source: https://github.com/sommio/RSSift/tree/main/.agents/skills/ce-work
Command: npx skills add https://github.com/sommio/RSSift --skill ce-work-sommio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and standardizes the end-to-end execution of planned work items, helping teams ship complete features with consistent quality.

Core Features & Use Cases

  • Plan-driven execution: Interpret plans or prompts and stage work in a structured, repeatable manner.
  • Incremental delivery: Break work into tasks, run validations, and commit changes in meaningful units.
  • Guardrails and reviews: Enforce testing coverage, adherence to project conventions, and timely code reviews.

Quick Start

Provide a plan document or bare prompt describing the work, and ce:work will triage, plan, and execute to ship a complete feature.

Frequently Asked Questions about ce:work

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

FAQPage Schema
How do I automate work plan execution to ship complete features?

Automating work plan execution involves using a tool to triage tasks, run execution loops, validate with tests, and commit changes incrementally. This enforces guardrails like consulting the plan and adhering to project patterns to ship complete features safely.

What is incremental commit in plan-driven software development?

Incremental commit in plan-driven software development is breaking work into structured tasks, running validations on each unit, and committing changes progressively. This ensures consistent quality and meaningful delivery units throughout the execution loop.

Does plan-driven execution work for operational tasks and product delivery?

Yes, plan-driven execution works for operational tasks and product delivery. The process interprets plans or prompts to stage work in a repeatable manner, applying guardrails like testing coverage and code reviews across task discovery and execution.

How do I enforce code review and testing coverage during feature delivery?

To enforce code review and testing coverage during feature delivery, you apply execution guardrails that require running tests, updating task status, and adhering to project conventions before allowing incremental commits. This standardizes end-to-end quality.

What are the limitations of automating execution with bare prompts?

When automating execution with bare prompts, the process relies entirely on automated triage and planning to interpret the work. While it stages tasks and enforces guardrails, highly ambiguous prompts may lack the detailed project patterns needed for precise implementation.

Can I use ce:work to structure task discovery and execution loops?

Yes, ce:work can structure task discovery and execution loops. It interprets provided plan documents or prompts to discover tasks, run execution loops, enforce testing, and manage incremental commits for shipping complete features.