ce-work

Execute software development plans into complete, tested features with git workflow.

1|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/lumenhelixsolutions/HOOTai --skill ce-work-lumenhelixsolutions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-work
Source: https://github.com/lumenhelixsolutions/HOOTai/tree/main/skills/compound-engineering/cache/ce-work
Command: npx skills add https://github.com/lumenhelixsolutions/HOOTai --skill ce-work-lumenhelixsolutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of incomplete, inconsistent, or low-quality feature implementations when executing work from plans or work prompts, removing guesswork and ensuring you ship fully functional, tested features every time.

Core Features & Use Cases

  • Intelligent Work Triage: Automatically routes trivial, small, or large work to the appropriate execution path, and detects non-code plans to use specialized workflows.
  • End-to-End Execution Lifecycle: Manages git branch setup, task breakdown, test discovery, incremental commits, subagent dispatch for parallel work, and quality checks.
  • Quality Enforcement: Enforces continuous testing, adherence to existing code patterns, and mandatory review gates to maintain codebase health.
  • Use Case: If you have a plan to add user authentication to your app, this Skill will break the work into tasks, set up your feature branch, run tests as you build, handle merge conflicts for parallel work, and ship the complete feature without leaving partial work behind.

Quick Start

Use the ce-work skill to execute the feature plan at docs/plans/user-auth.md and ship the complete, tested implementation following your project's existing patterns.

Frequently Asked Questions about ce-work

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

FAQPage Schema
How do I implement a feature plan from start to finish without leaving partial work behind?

Feature implementation from plan documents is executed end-to-end by breaking work into tasks, setting up git branches, running continuous tests, and shipping complete, tested features without partial implementations.

What is the best way to manage git workflow and incremental commits for cross-cutting architectural changes?

Managing git workflow for architectural changes involves routing work through task breakdown, subagent dispatch for parallel execution, and enforcing incremental commits with mandatory quality gates to maintain codebase traceability.

Can I execute trivial code fixes and large feature plans using the same structured workflow?

Trivial fixes and large features can both be executed using an intelligent work triage system that automatically routes work to the appropriate execution path based on complexity and scope.

How does subagent orchestration handle parallel work and merge conflicts during feature shipping?

Subagent orchestration dispatches parallel work across tasks while continuous testing and quality enforcement manage conflicts, ensuring adherence to existing code patterns throughout the feature shipping lifecycle.

Do I need a detailed plan document to start executing software development work?

A detailed plan document is not required; software development work can be executed from bare prompts, with the system automatically detecting non-code plans to apply specialized workflows as needed.

Why does test discovery matter when shipping complete features incrementally?

Test discovery matters because it enforces continuous testing and mandatory review gates during incremental commits, ensuring that shipped features maintain codebase health and adhere to existing project patterns.