cs-epic

Decompose large requirements into approved deliverable sub-items and execute them across sessions.

1.1k|83|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/liuzhengdongfortest/easysdd --skill cs-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cs-epic
Source: https://github.com/liuzhengdongfortest/easysdd/tree/main/plugins/codestable/skills/cs-epic
Command: npx skills add https://github.com/liuzhengdongfortest/easysdd --skill cs-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Large or system-level requirements are too big to implement in one pass: the route is unclear, decisions depend on each other, and work spans multiple sessions. This Skill turns a vague big requirement into a reviewed, owner-approved Epic contract, then drives each deliverable sub-item to completion with evidence and milestone commits.

Core Features & Use Cases

  • Route discovery and decomposition: Converge route-level uncertainty into a proposed Epic with goals, scope, acceptance criteria, decision nodes (AFK/HITL), and sub-item contracts, using wayfinding and shared-language references.
  • Dual-layer state management: Keep a permanent Epic document as the single source of truth and a work cursor (.codestable/work/epic-{slug}.md) for resumable execution state, approved revision hashes, and per-item progress.
  • Governed execution: Enforce owner gates, fresh-reviewer design/contract/final-acceptance reviews, semantic-atomic milestone commits, and optional parallel sub-item execution with isolated workers.
  • Use Case: You need to add a multi-module billing capability. The Skill drafts a proposed Epic, resolves route decisions with you, gets the plan reviewed and approved, then executes each sub-item through cs-feat/cs-issue/cs-refactor with verification evidence until final acceptance.

Quick Start

Ask the agent to break down and drive your large requirement, for example: use cs-epic to plan and execute the migration of our billing system to usage-based pricing.

Frequently Asked Questions about cs-epic

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

FAQPage Schema
How do I break down a large feature request into executable tasks?

Invoke cs-epic with the requirement description. It runs bounded route discovery, drafts a proposed Epic with goals, scope, acceptance criteria, and sub-item contracts, then requires your confirmation and a design review before executing each sub-item.

When should I use cs-epic instead of cs-feat or cs-issue?

Use cs-epic when the work is a large or system-level capability needing decomposition into multiple deliverable sub-items. Single features go to cs-feat and bug fixes go to cs-issue; cs-epic delegates sub-items to those owning skills.

Can an Epic resume after the session ends?

Yes. State lives in a work cursor at .codestable/work/epic-{slug}.md recording the approved revision hash, phase, current item, and progress. On resume, the Skill verifies the permanent Epic document hash against repository facts before continuing.

Does cs-epic support parallel execution of sub-items?

Yes, when the owner approves item_progression: parallel with authorized milestone commits. The main flow dispatches workers to isolated workspaces, integrates deliveries serially, re-runs verification, and remains the single writer of shared state.

What approvals are required before cs-epic writes code?

The decomposition plan must pass a fresh-reviewer design review and an owner gate confirming goals, scope, acceptance, sub-item contracts, and commit/publish strategies. Execution, milestone commits, and remote publishing each follow the approved strategy only.