lean-company
Skill8 starsChanged 3 months agoMITView on GitHub
Run one small piece of work through this company with the hierarchy and the paperwork cut to the bone and every gate fully intact - the CEO dispatches a developer directly, writes a ten-line brief, dispatches one deliberate audit, and merges on green. Use ONLY when the user types /lean-company. Anything touching a frozen surface, a migration, auth or billing or money, an invariant, or a second workstream belongs in /company instead.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- brainstormSkill
- company-initSkill
- companySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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 16
Not initialized. Frozen surface.
- Distinctive: line 35
Run the gates that cover the change, or the suites this project's CLAUDE.md names.
- Distinctive: line 40
No spec, no PM, no architect, no tech-lead, no witness curation, no docs-librarian, no report template, no retrospective.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
/lean-company - the fast door, same gates
Cuts hierarchy and paperwork. Never cuts gates. A fast path that drops gates is Claude Code with extra steps, which everyone already has.
The work: $ARGUMENTS
Wrong door - stop and run /company
Not initialized. Frozen surface. Migration. Auth, billing, or money. Invariant. Second workstream. One-way: does not come back.
The run
- Short spec to
company/specs/spec-<slug>.md, then a pointer brief tocompany/briefs/brief-<slug>.md(spec link, owned paths, outcome). The spawn prompt carries the spec path plus the paths - not a restatement.guard_specrequires the brief file; it also survives this session dying. - Targeted Edit adding your entry in
company/state/active-task.json. Classify honestly (quickorfeature). Never rewrite the whole file. - One
developerin a worktree (git worktree add .claude/worktrees/<slug> -b task/<slug>). Two only on disjoint paths. No tech-lead. - QA only if there is a screen to drive (four states). Else the tests are the evidence.
- One
auditoron purpose, once, on the finished diff. Delegated worktree work does not arm the self-authorship audit, and lean mode deleted the lead. Dispatch it by hand. - Run the gates that cover the change, or the suites this project's
CLAUDE.mdnames. If you already ran them this session, stamp and merge. Do not re-run because the stamp file is stale. - Merge. Remove ONLY your entry. One RESUME row. Report what shipped.
No spec, no PM, no architect, no tech-lead, no witness curation, no docs-librarian, no report template, no retrospective.
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.

