Extracting Requirements
prime-radiant-inc/iterative-development
Reads human-written spec documents and produces per-epic requirement files with proof obligations plus behavior scenarios with stable IDs, using parallel chunked extraction.
A skill your agent uses when a complex, long-running task risks polluting one conversation — research, implementation, review, planning, or learning that should be split into dependency-aware…
Install Conductor Cc
$ npx skills add Jinghao67/conductor --skill conductor-cc -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jinghao67/conductor conductor-cc --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jinghao67/conductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-code/skills/conductor-cc .claude/skills/conductor-cc && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "conductor-cc" agent skill from https://github.com/Jinghao67/conductor/tree/main/claude-code/skills/conductor-cc into .claude/skills/conductor-cc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-cc", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jinghao67/conductor/tree/main/claude-code/skills/conductor-ccType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jinghao67/conductor --skill conductor-cc -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jinghao67/conductor conductor-cc --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jinghao67/conductor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude-code/skills/conductor-cc .agents/skills/conductor-cc && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "conductor-cc" agent skill from https://github.com/Jinghao67/conductor/tree/main/claude-code/skills/conductor-cc into .agents/skills/conductor-cc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-cc", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jinghao67/conductor --skill conductor-cc -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jinghao67/conductor conductor-cc --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jinghao67/conductor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude-code/skills/conductor-cc .cursor/skills/conductor-cc && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "conductor-cc" agent skill from https://github.com/Jinghao67/conductor/tree/main/claude-code/skills/conductor-cc into .cursor/skills/conductor-cc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-cc", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jinghao67/conductor.git --path claude-code/skills/conductor-cc--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jinghao67/conductor --skill conductor-cc -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jinghao67/conductor conductor-cc --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jinghao67/conductor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude-code/skills/conductor-cc .gemini/skills/conductor-cc && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "conductor-cc" agent skill from https://github.com/Jinghao67/conductor/tree/main/claude-code/skills/conductor-cc into .gemini/skills/conductor-cc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-cc", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jinghao67/conductor conductor-ccInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jinghao67/conductor --skill conductor-cc -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jinghao67/conductor.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude-code/skills/conductor-cc .github/skills/conductor-cc && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "conductor-cc" agent skill from https://github.com/Jinghao67/conductor/tree/main/claude-code/skills/conductor-cc into .github/skills/conductor-cc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-cc", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jinghao67/conductor --skill conductor-cc -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jinghao67/conductor conductor-cc --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jinghao67/conductor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude-code/skills/conductor-cc .opencode/skills/conductor-cc && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "conductor-cc" agent skill from https://github.com/Jinghao67/conductor/tree/main/claude-code/skills/conductor-cc into .opencode/skills/conductor-cc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conductor-cc", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
conductor-cc- GitHub stars
- 102
- Token cost
- ~1.1k tokens
- SKILL.md length
- 494 words
- Files
- 4 (incl. references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a complex, long-running task risks polluting one conversation — research, implementation, review, planning, or learning that should be split into dependency-aware…
- Works in 6 steps: Routing — where does a request belong? → Dependency / wave planning — never… → What to merge — at /cd-merge, compress… → …
- Long-running task risks polluting one conversation — research
- SKILL.md covers The one principle, What the harness enforces for…, What YOU must judge (the soft… and Commands (the verbs), plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Conductor Cc is an agent skill from Jinghao67/conductor. Use when a complex, long-running task risks polluting one conversation — research, implementation, review, planning, or learning that should be split into dependency-aware branches while keeping the master session clean. The Claude Code-native Conductor, where branches are separate user-driven sessions, raw content is quarantined in subagents, and the protocol is enforced by hooks rather than only guidance. Pairs with grill-me-style requirement work.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/branch-brief-template.md`, `references/branch-map-template.md` and `references/completion-report-template.md`).
It sits in Agent Workflows, covering Requirements gathering and Subagents. The repository describes itself as: Context conductor for clean master sessions, dirty explainer sidecars, and interactive AI branches. The licence is MIT.
When your agent uses it
- Long-running task risks polluting one conversation — research
- Learning that should be split into dependency-aware branches while keeping the master session clean
Example prompts
- “/conductor-cc”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Routing — where does a request belong?
- Dependency / wave planning — never assume all branches run in parallel. Classify each: ready_parallel (runs now from the current…
- What to merge — at /cd-merge, compress to a short approved record, normalize terminology, and separate proposed global decisions for…
- Card before session — create a branch card + brief (/cd-branch) before anyone opens a session. If dependencies are ambiguous, ask the user…
- Staleness — if the master snapshot advances in a way that invalidates an active brief, mark it stale and offer to refresh; don't silently…
- Global decisions — a decision made inside a branch is not binding until confirmed in the master.
What it can do on your machine
Read from SKILL.md and the folder at commit b866a50. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Conductor Cc loads about 1.1k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 494 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Jinghao67/conductor at commit b866a50, republished under its MIT licence (© Jinghao67). 494 words, ~1,078 tokens.
Download SKILL.mdSave it as
.claude/skills/conductor-cc/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- conductor-cc
- description
- Use when a complex, long-running task risks polluting one conversation — research, implementation, review, planning, or learning that should be split into dependency-aware branches while keeping the master session clean. The Claude Code-native Conductor, where branches are separate user-driven sessions, raw content is quarantined in subagents, and the protocol is enforced by hooks rather than only guidance. Pairs with grill-me-style requirement work.
Conductor (Claude Code)
A context-isolation + branch-registry protocol for Claude Code. One master session stays clean; messy work happens in separate branch sessions and throwaway subagents. Unlike a plain skill, the hard rules here are enforced by hooks, not by your goodwill — so this skill only has to carry the judgment the hooks can't.
The one principle
The master holds only distilled knowledge. All raw content is quarantined.
| Raw content | Quarantine | Master gets |
|---|---|---|
| a branch's messy history | a separate user-driven session | a completion report |
| codebase source | the Explore subagent | conclusion + file:line anchors |
| paper/web content | the cd-research subagent | distilled notes + sources |
What the harness enforces for you (don't re-litigate it)
- SessionStart hook injects role context: master → snapshot + Today View; a bound branch → only its brief. A branch literally cannot see master/sibling history.
- PreToolUse hook = three gates: (a) read-firewall — broad/external reads in master are denied, forcing you to delegate to Explore/cd-research; (b) merge-gate — the master snapshot can't absorb a branch without an approved report; (c) branch-write-guard — a branch can't write master records.
- PostToolUse hook keeps
registry.json→branch-map.mdin sync and performs privileged state transitions.
When a read is denied in the master, that is by design: spawn an Explore subagent for codebase questions, or cd-research for web/papers, and absorb only the returned conclusion. Do not fight the firewall; /cd-status --unlock exists if the user truly needs it off.
Show full SKILL.md (269 more words)Show less
What YOU must judge (the soft layer)
- Routing — where does a request belong?
- master: changes to goals, scope, constraints, the branch map, merges, snapshots.
- a branch: exploratory / implementation / research / review work with many intermediate details.
- explainer sidecar: long explanations, tutorials, "I don't fully get this yet."
- Dependency / wave planning — never assume all branches run in parallel. Classify each:
ready_parallel(runs now from the current snapshot),dependent(needs another branch's output),gate(a review/merge/decision),optional,explainer. Only open current-wave branches. Keep ≤2 active interactive branches; suggest parking/archiving before a third. - What to merge — at
/cd-merge, compress to a short approved record, normalize terminology, and separate proposed global decisions for explicit user confirmation. Reject reports that don't meet the brief (the cd-merge-verify subagent backs you up). Explainer output never merges by default. - Card before session — create a branch card + brief (
/cd-branch) before anyone opens a session. If dependencies are ambiguous, ask the user before creating threads. - Staleness — if the master snapshot advances in a way that invalidates an active brief, mark it stale and offer to refresh; don't silently sync.
- Global decisions — a decision made inside a branch is not binding until confirmed in the master.
Commands (the verbs)
/cd-init · /cd-branch · /cd-enter → /cd-bind (in the new tab) · /cd-status · /cd-complete (in the branch) · /cd-merge (in the master).
Session names
[CD-MAIN][master] <project> · [CD-001][W1][<role>] <purpose> · [CD-E01][sidecar][explainer] Dirty questions. Never put mutable status (active/done/blocked) in a title — that lives in the registry/Today View.
Branch lifecycle
planned → brief_ready → active → (completion_suggested) → report_ready → merge_pending → merged | rejected → archived (or blocked). State is in .conductor/registry.json; the human view in .conductor/branch-map.md is rendered from it.
© Jinghao67, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in claude-code/skills/conductor-cc of Jinghao67/conductor.
- SKILL.md
- references/branch-brief-template.md
- references/branch-map-template.md
- references/completion-report-template.md
Open the folder on GitHubat commit b866a50
Compare with similar skills
Conductor Cc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conductor Cc this skillJinghao67/conductor | 102 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Extracting Requirementsprime-radiant-inc/iterative-development | 181 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Grill Articleopen-cqrs/opencqrs | 118 | — | ~5k | Automated safety check: Notes | Apache-2.0 | |
| AutodevZhangShenao/harness9 | 141 | — | ~606 | Automated safety check: Notes | MIT | |
| Cxas Protocol Robust ExtractionGoogleCloudPlatform/cxas-scrapi | 107 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Grill Article
open-cqrs/opencqrs
Critically inspect a written article before enrichment — verify codebase claims with real tool lookups, find internal contradictions, and (for argumentative articles) sparr with the author about…
Autodev
ZhangShenao/harness9
Feature auto-development — clarify requirements, generate spec, dispatch dev sub-agent to implement and merge into current branch
Cxas Protocol Robust Extraction
GoogleCloudPlatform/cxas-scrapi
A robust methodology for LLM-based requirements gathering and high-fidelity artifact generation.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from Jinghao67/conductor
Conductor
Jinghao67/conductor
A skill your agent uses when a complex task needs dependency-aware interactive branches, subagents, or AI coding threads while keeping the master session context clean through explicit branch…
Related
Categories
Questions about Conductor Cc
What does Conductor Cc do?
A skill your agent uses when a complex, long-running task risks polluting one conversation — research, implementation, review, planning, or learning that should be split into dependency-aware…. Conductor Cc is an agent skill from Jinghao67/conductor. Use when a complex, long-running task risks polluting one conversation — research, implementation, review, planning, or learning that should be split into dependency-aware branches while keeping the master session clean.
When should I use Conductor Cc?
Conductor Cc fits situations like: long-running task risks polluting one conversation — research; learning that should be split into dependency-aware branches while keeping the master session clean.
How do I install Conductor Cc in Claude Code?
Run `npx skills add Jinghao67/conductor --skill conductor-cc -a claude-code`. Or copy the skill folder (claude-code/skills/conductor-cc in Jinghao67/conductor) into .claude/skills/conductor-cc in your project. Claude Code loads it when a task matches its description.
How do I install Conductor Cc in Codex?
Run `npx skills add Jinghao67/conductor --skill conductor-cc -a codex`. Or copy the skill folder (claude-code/skills/conductor-cc in Jinghao67/conductor) into .agents/skills/conductor-cc in your project. Codex loads it when a task matches its description.
Can I use Conductor Cc in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jinghao67/conductor --skill conductor-cc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conductor-cc, .gemini/skills/conductor-cc, .github/skills/conductor-cc and .opencode/skills/conductor-cc in your project.
What does Conductor Cc need to run?
SKILL.md names no scripts, command-line tools or credentials: Conductor Cc is instructions for the agent only.
Does Conductor Cc access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Conductor Cc safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Conductor Cc use?
Conductor Cc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Conductor Cc use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 665 tokens, read only when the agent opens those files.
What are the alternatives to Conductor Cc?
Skills that share tags, products or a category with Conductor Cc: Extracting Requirements (prime-radiant-inc/iterative-development, 181 stars), Grill Article (open-cqrs/opencqrs, 118 stars), Autodev (ZhangShenao/harness9, 141 stars) and Cxas Protocol Robust Extraction (GoogleCloudPlatform/cxas-scrapi, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conductor Cc?
Jinghao67 (a GitHub user) maintains it in Jinghao67/conductor, which has 102 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on June 10, 2026.
Source: Jinghao67/conductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.