cc-work

Orchestrate end-to-end task execution with worker isolation, verification, and review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end task execution with worker isolation, verification, and review manages the full lifecycle from task intake to completion in isolated contexts.

Core Features & Use Cases

  • Orchestrates: pick task → optional worktree → spawn worker → verify → review → done → loop.
  • Supports multiple modes (worktree isolation, new feature branches, or current work context) and integrates with cc-plan and epic-review for a closed-loop workflow.
  • Use Case: teams needing repeatable task execution with per-task isolation, automated checks, and auditable progress across epics and tasks.

Quick Start

cc-flow go "implement authentication" to trigger an epic that cc-work will execute end-to-end with worker isolation.

Frequently Asked Questions about cc-work

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

FAQPage Schema
What is worker isolation for task execution workflows?

Worker isolation for task execution is the process of managing individual workstreams in separate contexts. It ensures repeatable execution by isolating changes, verifying outputs, and tracking progress across epics without conflicts.

How do I automate end-to-end task execution with automated checks?

Automate end-to-end task execution by triggering an epic via a command. The workflow then orchestrates picking tasks, spawning isolated workers, verifying results, and looping until completion.

Does this task execution workflow support git worktree isolation?

Yes, the task execution workflow supports git worktree isolation. It offers multiple modes including worktree isolation, new feature branches, or operating within the current work context.

Can I use this for repeatable task execution across multiple epics?

Yes, you can use this for repeatable task execution across multiple epics. It integrates with planning and review tools to manage auditable progress and maintain a closed-loop workflow.

What is the best way to manage per-task worktrees in software engineering?

The best way to manage per-task worktrees is using an orchestration workflow that spawns isolated workers for each task. This approach ensures automated checks and auditable progress without manual branch management.