ce-work

Execute work plans into test-driven tasks with branch creation and PR validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates fragmented development progress and "80% done" features by turning a plan, specification, or todo file into a disciplined, test-driven execution workflow that finishes complete, reviewed work.

Core Features & Use Cases

  • Clarification & Planning: Read the input plan, surface ambiguities, and require user approval before implementation.
  • Branching & Isolation: Recommend and automate branch or worktree creation to avoid committing directly to default branches.
  • Task Execution Loop: Break plans into prioritized TodoWrite tasks, implement following existing code patterns, write tests, run integration checks, and perform incremental commits.
  • Quality & Release Controls: Run linting and full test suites, capture UI screenshots for PRs when applicable, and include post-deploy monitoring and rollback guidance in PR descriptions.
  • Use Cases: Implement new features, fix bugs with lifecycle checks, and deliver UI changes with screenshot evidence and operational validation.

Quick Start

Provide a work plan file and ask the skill to convert it into a prioritized task list, create a feature branch or worktree, and begin implementing tasks with tests and incremental commits.

Frequently Asked Questions about ce-work

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

FAQPage Schema
How do I execute a work plan to deliver complete, tested software features?

To execute a work plan, provide a specification or todo file to convert it into prioritized tasks, create an isolated branch, and implement with continuous testing and incremental commits.

How do I automate branch creation and task tracking for feature development?

Automate branch creation and task tracking by providing a work plan file, which prompts the creation of a feature branch or worktree and breaks the plan into prioritized TodoWrite tasks.

What is the best way to ensure a pull request includes post-deploy validation and rollback guidance?

To ensure pull requests include post-deploy validation, implement features using a disciplined execution workflow that captures UI screenshots, runs full test suites, and generates rollback guidance in PR descriptions.

Can I use this workflow for bug fixes and UI updates, not just new feature development?

Yes, you can use this workflow for bug fixes and UI updates, applying lifecycle checks and capturing screenshot evidence alongside operational validation for pull requests.

Does this feature development workflow require me to clarify ambiguities before implementation?

Yes, this workflow requires clarification, surfacing ambiguities in the input plan and requiring explicit user approval before writing any code or creating branches.

Why should I avoid committing directly to default branches during code execution?

You should avoid committing directly to default branches to maintain isolation and code quality, as this workflow recommends and automates branch or worktree creation before implementing tasks.