cpm:do

Automate end-to-end execution of epic-driven development tasks into Claude Code.

Updated Oct 11, 2025

Search Tags:#automation #verification #task-execution #retro #epic-doc #progress-file

Ready to run

npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-do

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cpm:do
Source: https://github.com/ninthspace/claude-code-marketplace/tree/main/cpm/skills/do
Command: npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-do

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end execution of work defined in epic documents. It hydrates the next unblocked story, creates Claude Code tasks for each required ###, runs verification gates, updates epic status, and persists progress for resilience.

Core Features & Use Cases

Hydrates stories and tasks from epic documents into Claude Code's task system.
Creates and manages implementation tasks and a verification gate per story.
Updates status in the epic doc and records retro observations for continuous improvement.
Maintains a resilient progress trail via a central progress file to survive context compaction.
Supports planning modes and integration with test verification flows as defined by the epic.

Quick Start

Run /cpm:do to start the epic-driven task execution loop.

Frequently Asked Questions about cpm:do

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

FAQPage Schema

How do I automate task execution from epic documents in my development workflow?▼

Epic-driven task execution is automated by hydrating stories from epic documents into a task system. This Skill manages the loop by creating implementation tasks, running verification gates, and persisting progress to survive context compaction.

What is the best way to track progress across complex stories during automated task execution?▼

Progress tracking across complex stories is managed via a central progress file. This resilient trail records task statuses and retro observations, ensuring execution survives interruptions and context compaction without losing state.

Can I integrate verification gates and testing steps into epic-driven development automation?▼

Yes, verification gates and testing steps integrate directly into epic-driven development automation. The execution loop creates a verification gate per story and coordinates with test verification flows as defined by the epic document.

How do I hydrate unblocked stories into a task system for end-to-end execution?▼

Hydrating unblocked stories into a task system requires parsing epic documents to identify the next actionable story. The Skill then automatically generates corresponding implementation tasks and verification gates for execution.

Does epic-driven task execution support planning modes before creating implementation tasks?▼

Yes, epic-driven task execution supports planning modes before creating implementation tasks. This allows you to review the hydrated story structure and coordinate testing steps before committing to the execution loop.