endurance
Skill0 starsChanged 44 days agoNo licenceView on GitHub
Act as the tech lead for several features built in parallel, each in its own git worktree — and make delivery faster over time without lowering quality. From the main worktree, shows a board of every feature in flight (stage, owner, worktree, PR, who's waiting on what), catches conflicts early — between plans before code exists, between branches, and by merging all active branches together and running the tests — decides the merge order (stacking dependent features), keeps work-in-progress limited, starts new features in bootstrapped worktrees, and delegates the code-heavy stages to background worker subagents that talk to each other through a shared message channel and whose decisions it batches and puts to the user. Tracks how long each feature and stage takes (active time, waiting on the user, rework, CI and delivery time) with quality counters beside it, finds the bottleneck and proposes changes that shorten build and delivery. Watches PRs and notifies the user when something needs them. Never decides for the user, never removes a quality gate, never merges unasked. Use when working on several features at once, to see delivery metrics, or whenever the user says "endurance", "tech lead", "orchestre les features", "plusieurs features en parallèle", "où en sont toutes les features", "dashboard des features", "combien de temps pour livrer", or "livrer plus vite".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- soophoo/skillsword for word, first seen Sep 30, 2026
- shoushouo/disco-elysium-plugin-for-cursortheir own version, first seen Apr 5, 2026
- liigoQi/disco-elysiumtheir own version, first seen Apr 4, 2026
Other versions3 projects use a version of this.
Word for word · 1
- soophoo/skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 2
- liigoQi/disco-elysium★ 96same name
- shoushouo/disco-elysium-plugin-for-cursor★ 4same name
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
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.