lead
Skill2 starsChanged 33 days agoMITView on GitHub
Make this Claude Code session the project's lead session (or, in a project built as streams, one stream's lead), where code-kit's loop runs and the plan's stories are dispatched from, when several sessions work one project. Running it moves the lead here as the person sends it; the skill confirms it and says what it means. Use when the person says this session should lead, asks which session leads, or runs /code-kit:lead.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- igoroliveirg/claude-copytheir own version, first seen Nov 15, 2026
- Palatine-Labs/conisotheir own version, first seen Nov 15, 2026
- microsoft/vscode-documentdbtheir own version, first seen Nov 8, 2026
- tristanphvn/keeltheir own version, first seen Nov 8, 2026
- AJschoons/robowrighttheir own version, first seen Nov 8, 2026
- Devolutions/IronRDPtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use reflect, technical-writing and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillreflect
Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections ("no", "wrong"), praise ("perfect", "exactly"), or when discovering edge cases. Complements .squad/agents/{agent}/history.md and .squad/decisions.md.
Also in 4 projects that use this
VercelSkilltechnical-writing
Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current source, tests, CLI help, public releases, and repository conventions.
Also in 3 projects that use this
photon-groveSkillunslop
Detects and rewrites generic, overly polished, or AI-sounding prose while preserving meaning. Use when the user asks to "unslop", humanize, de-AI, tighten, or review whether writing sounds generated.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 4 projects that use this
- VercelSkill
setup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- Devolutions/IronRDP★ 3.3ksame name
- keli-wen/agy-staff★ 828same name
- robertguss/claude-code-toolkit★ 118same name
- microsoft/vscode-documentdb★ 33same name
- Palatine-Labs/coniso★ 17same name
- igoroliveirg/claude-copy★ 9same name
- Kripu77/software-factory★ 7same name
- xiebaiyuan/xiebaiyuan-skills★ 6same name
- alexnthnz/keel★ 5same name
- gao-xh/multi-agent-protocol★ 4same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
If this session already leads, say so and stop.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lead from this session
Several Claude Code sessions can work one project at once. One is the lead session: code-kit's loop runs there, and the plan's stories are dispatched from it. The others are working sessions: they stay quiet (no loop prompts, no other session's decisions), and each records its ad hoc task, with the paths it leases, before it changes code.
The CLI is node "${CLAUDE_PLUGIN_ROOT}/bin/code-kit.mjs", run from the project root.
When the person ran /code-kit:lead, typing it was their choice: code-kit recorded this session as the lead (of the stream they named) as the prompt arrived, and its note in your context says so, or why it couldn't. Don't ask them to run anything. Run who to confirm, and tell them in a sentence or two what it means: which stream this session leads, its lanes and plan, and which session leads the rest. When the note says another lead holds the main checkout, move this session into a worktree of its own on the branch the note names (EnterWorktree) before you change anything. If the note says it couldn't (a stream that doesn't exist, say), tell them why and what the streams are.
node "${CLAUDE_PLUGIN_ROOT}/bin/code-kit.mjs" whoWhen the person asked in words ("lead from this session"), and didn't run the command:
See who leads now:
node "${CLAUDE_PLUGIN_ROOT}/bin/code-kit.mjs" who node "${CLAUDE_PLUGIN_ROOT}/bin/code-kit.mjs" sessions- If this session already leads, say so and stop.
- Otherwise, tell them what moving the lead does: this session starts running the loop and dispatching the plan's stories, and the session that led becomes a working session, which stops prompting its lead. Choosing the lead is theirs, and the hooks refuse it from an agent: they run
/code-kit:lead(with the stream, in a project built as streams), or use Lead from here in the code-kit band.
A project built as streams (code-kit streams lists them; spec 31) has a lead per stream, and they lead at once: each runs its own loop, dispatches only its own stream's lanes and stories, and writes only its own stream's plan and specs. The argument names the stream (/code-kit:lead studio).
Moving one stream's lead leaves the other streams' leads as they are. The first lead works in the main checkout; every other stream's lead works in a worktree of its own (start the session with claude --worktree, or move it into one), on lead/<stream>, and its plan changes reach the base through the merge queue. A session that leads with no stream named leads every stream that has no lead of its own. A working session joins a stream with sessions stream <name>, the person's command too.
A working session doesn't need this to work: it records its task (code-kit task "<what>" --touches "<globs>"), works in a worktree of its own, and code-kit task done when it's finished.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.