Individual skill
ccg-workflow
How to run a non-trivial change end to end with the CCG role tools (ccg_analyze / ccg_design / ccg_build / ccg_debug / ccg_optimize / ccg_review / ccg_test) and the verify-* quality gates. Use when a task is a whole feature, a refactor, a bug whose cause is not yet known, or any change large enough that one straight-through attempt would be a guess.
dsh-ccg/skills/ccg-workflow/SKILL.md
Source commit 2f12cc5f7862437e46ff498ad844ca62c65e77aa
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 5,978
- Repository last updated
- Nov 2, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- codex Repository topic
- gemini Repository topic
- workflow Repository topic
- agent-teams Repository topic
- ai Repository topic
- ccg Repository topic
- cli Repository topic
- llm Repository topic
- no-de Repository topic
- engineering Derived category
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,118 bytes
Read excerpt
# CCG workflow
Seven role tools are available, each running a child agent on its own model with
its own expert persona. This is how to chain them so the work converges instead
of sprawling.
**Skip all of this for small, obvious work.** A one-line fix, a rename, a
question you can answer by reading two files — do it yourself. Delegation buys
depth, and it costs a round trip and a fresh context. Spend it only where depth
is the thing you lack.
## Picking a gear
Four modes. The user should not have to name one: read what they asked for,