lead
Skill7 starsChanged 3 months agoMITView on GitHub
Use when acting as the factory tech lead: classify work, ask the minimum questions, create tickets, and dispatch without implementing.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- xiebaiyuan/xiebaiyuan-skillstheir own version, first seen Nov 1, 2026
- Rhovian/nilestheir own version, first seen Nov 1, 2026
Used with
Projects with it also use reflect, technical-writing and 2 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
- Microsoft AzureSkill
design
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 3 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 versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- Devolutions/IronRDP★ 3.3ksame name
- keli-wen/agy-staff★ 828same name
- robertguss/claude-code-toolkit★ 118same name
- microsoft/vscode-documentdb★ 33same name
- xiebaiyuan/xiebaiyuan-skills★ 6same name
- alexnthnz/keel★ 5same name
- gao-xh/multi-agent-protocol★ 4same name
- Rhovian/niles★ 4same name
- AhmedMerza/agent-skills★ 2same name
- AhmedMerza/claude-skills★ 2same name
4 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.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- browser-useSkill
- code-reviewSkill
- implementSkill
- loop-on-ciSkill
- mermaidSkill
- run-smoke-testsSkill
- tddSkill
- to-ticketsSkill
- unslopSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 8
Read lanes/tech-lead.md and AGENTS.md.
- Very specific: line 12
After tickets exist, start factory.sh floor, or one factory.sh lane.
“Common” is measured: kept by at least 6 in 10 of the 13 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
Factory lead
Read lanes/tech-lead.md and AGENTS.md. Follow factory-to-tickets. Ask Telemetry when production data exists. Do not implement. Do not merge.
At the start, run factory.sh mem read for the issue, or for the project if there is no issue. Empty memory is fine. GitHub is the source of truth when local memory has no rows.
After tickets exist, start factory.sh floor, or one factory.sh lane. Dispatch through factory.sh only. Do not implement, review, or watch CI in the lead session.
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.