help
Skill0 starsChanged 3 months agoMITView on GitHub
Which /co-founder skill fits the current situation. Run when the user asks "which skill", "what should I use", "how does co-founder work", or describes a task without knowing where it goes.
82 other projects use a version of this.
Adopted by
Most recently taken up by
- krystaleicher/claude-skillstheir own version, first seen Nov 16, 2026
- rzaaeeff/agent-ledgertheir own version, first seen Nov 16, 2026
- tatashbar/Economic-Modeling-Studiotheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
Used with
Projects with it also use create-stories, story-done and 10 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.
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 9 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 9 projects that use this
- +10 more from lilangMax
Other versions82 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 82
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- bitwize-music-studio/claude-ai-music-skills★ 668same name
- waynesutton/markdown-site★ 628same name
- andrew-shwetzer/career-ops-plugin★ 501same name
- andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-★ 500same name
72 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
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 63 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Read references/CONVENTIONS-core.md and apply its Help exception.
- Distinctive: line 42
Ask before you assert: never present a quantity, duration, sample size, date, or causal motive in prose before asking the founder for it or …
“Common” is measured: kept by at least 6 in 10 of the 63 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
help: route to the right skill
Step 0: Preflight
Read references/CONVENTIONS-core.md and apply its Help exception. A Ready system
reads the "When you say X, I run Y" table in the founder's charter (AGENTS.md / CLAUDE.md).
Answer from it: name the ONE skill that fits what they described, say why in a sentence, and
give them the exact phrase to say. Two skills genuinely fit: name the order to run them in.
Resolve the two loaded collisions by intent. "Whether should we do/build/change this?" routes to the gauntlet; "how do we execute the decision already made?" routes to plan. For pricing, "should we change the price?" routes to the gauntlet; "how do we structure the approved price or offer?" routes to offer. State the distinction in one sentence when the wording is ambiguous.
Complete the whole routing hop before naming the skill. For any offer, price, spend, or other
money move, inspect wiki/business/offer.md and matching initiatives. An unresolved whether-call,
an unapproved price/offer, or a BIG move without a current SURVIVES verdict routes directly to
the gauntlet. Offer is the destination only when the exact move is already approved and the founder is
asking how to structure it. Never send the founder offer → gauntlet for a gate help could see now.
Resolve parked prerequisites before the owner skill. If the exact initiative says PARKED:
internal receipt missing, route first to the named measurement or recall action, then the gauntlet, then
offer after SURVIVES. If it says PARKED: external receipt missing, route research → gauntlet, then
offer after SURVIVES. An idea with no verdict routes to the gauntlet; a current SURVIVES verdict routes
to offer. Return the complete chain in three lines: Now, Then, After the gate.
Help answers the current prompt and stops. A new prompt replaces the prior routing task; help does not start steward, review, or any unrelated audit before returning the route. For "I want to charge 1,500. Set it up" against a price initiative parked on delivery evidence, the answer starts with that measurement, continues to the gauntlet, and reaches offer only after the gate survives.
Any Fresh, Partial, or Wrong-folder result stops and runs the co-founder-setup skill before anything else (re-sync for Partial).
Ask before you assert: never present a quantity, duration, sample size, date, or causal motive in prose before asking the founder for it or citing a receipt for it.
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.

