cw-execute

Execute a single native task board task through an 11-phase protocol.

14|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/sighup/claude-workflow --skill cw-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cw-execute
Source: https://github.com/sighup/claude-workflow/tree/main/skills/cw-execute
Command: npx skills add https://github.com/sighup/claude-workflow --skill cw-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables reliable execution of a single native task from a centralized task board by guiding and enforcing an 11-phase protocol, ensuring verifiable state and reproducible results.

Core Features & Use Cases

  • Orchestrates a deterministic single-task execution flow using the 11-phase protocol (orient, baseline, context, implement, verify-local, proof, sanitize, commit, verify-full, report, clean exit).
  • Integrates with the native task board through TaskList/TaskGet/TaskUpdate to load, execute, and mark task status in a controlled manner.
  • Produces structured proof artifacts and a summarized proof file to enable post-execution validation and auditing.
  • Suitable for development pipelines requiring repeatable task execution, traceability, and clean commits.

Quick Start

Invoke the cw-execute skill to run exactly one task from the native task board using the 11-phase protocol.

Frequently Asked Questions about cw-execute

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

FAQPage Schema
How do I execute a single task from a centralized task board with deterministic verification?

Yes, you can automate workflow verification for task execution by invoking a skill that applies an 11-phase protocol. This enforces rigorous local and full verification, producing structured proof artifacts for post-execution validation and auditing.

What is the 11-phase protocol for task execution and how does it work?

The 11-phase protocol for task execution is a deterministic sequence comprising orient, baseline, context, implement, verify-local, proof, sanitize, commit, verify-full, report, and clean exit. It guides state updates and ensures rigorous verification before marking task completion.

How do I generate auditable proof artifacts during automated task execution?

Generating auditable proof artifacts during automated task execution requires a protocol that enforces proof generation after local verification. This process produces a summarized proof file, enabling post-execution validation and ensuring traceable, reproducible development pipelines.

Does the task board execution protocol require any external dependencies or components?

The task board execution protocol requires no external dependencies or components. It integrates natively with TaskList, TaskGet, and TaskUpdate to load, execute, and mark task status in a controlled manner without needing additional environment setup.

When should I use a phased execution protocol for development workflows?

Using a phased execution protocol for development workflows is necessary when deterministic task completion, automated proof generation, and auditable commits are required. It ensures a clean state and reproducible results for pipelines demanding strict phase orchestration.