Skip to content
Back to search

company-factory

SkillWorks with Claude CodeGitHub

Describe a company in one config file. Get a team of Claude Code agents that runs it, and a live pixel office to watch them work.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/shouryaraj--company-factory/badge.svg)](/listings/shouryaraj--company-factory)

HTML

<a href="/listings/shouryaraj--company-factory"><img src="/api/listings/shouryaraj--company-factory/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 179 lines
  1. # company-factory
  2. **Describe a company in one config file. Get a team of Claude Code agents that runs it, and a live pixel office where you watch them work.**
  3. ![The office: agents at their desks, the Chief of Staff handing out tickets, handoffs walking to the shelf](docs/office.gif)
  4. You are the founder. You write `company.toml`: the mission, the roles, their skills, what needs your approval, the goals. `company-factory` turns it into a Claude Code workspace where:
  5. - the main session is your **Chief of Staff**: it plans, writes tickets, delegates and reviews;
  6. - every role is a **subagent** with a mission, owned folders, preloaded skills, hard "never" rules and a definition of done;
  7. - anything external, irreversible, financial or directional waits in **your approvals inbox**;
  8. - the **office** shows all of it live: who is working on what, which ticket is where, what is waiting on you.
  9. TypeScript on Node, one small runtime dependency, no cloud service. MIT.
  10. ## Try it in 30 seconds
  11. ```bash
  12. npx github:shouryaraj/company-factory demo
  13. ```
  14. This builds a sample company in a temp folder and opens its office with scripted activity. You only need Node 20+; no Claude session, no Taskboard. Other demos: `--example open-source` or `--example content-studio`.
  15. ## Prerequisites
  16. | Need | Why | Install |
  17. |---|---|---|
  18. | **Node 20+** | runs company-factory and the office hook | [nodejs.org](https://nodejs.org) |
  19. | **Claude Code** | runs the agents | [docs.claude.com/claude-code](https://docs.claude.com/en/docs/claude-code) |
  20. | **Taskboard** | the company's kanban board and its MCP server (`/setup-board`, tickets, the office board) | `brew tap tcarac/taskboard && brew install taskboard`, then `taskboard start` ([tcarac/taskboard](https://github.com/tcarac/taskboard)) |
  21. The examples use Taskboard. To skip it, set `[taskboard] enabled = false`: tickets then live in `company/board.md`.
  22. `company-factory doctor ./acme` checks all of this and tells you what is missing.
  23. ## Start your own company
  24. ```bash
  25. npm install -g github:shouryaraj/company-factory
  26. company-factory init ./acme --example saas # or starter, open-source, content-studio
  27. $EDITOR ./acme/company.toml # make it yours
  28. company-factory build ./acme # generate the workspace (safe to re-run)
  29. company-factory plugins ./acme --install # one-time: install the marketplace skills
  30. company-factory doctor ./acme # check Node, Claude Code, Taskboard, plugins
  31. taskboard start # terminal 1: the board (http://localhost:3010)
  32. company-factory office ./acme --open # terminal 2: the live office (http://127.0.0.1:4477)
  33. cd acme && claude # terminal 3: /setup-board once, then /kickoff <goal>, /standup
  34. ```
  35. ## What you get
  36. ```
  37. acme/
  38. company.toml the source of truth (you edit this)
  39. custom/{roles,skills,workflows}/ your own plug-ins; override built-ins with the same id
  40. CLAUDE.md generated: the Chief of Staff's operating manual
  41. .claude/agents/<role>.md generated: one subagent per role, skills preloaded
  42. .claude/skills/<skill>/ generated: the skills your roles use
  43. .claude/commands/ generated: /standup /kickoff /approvals /weekly-review /hire ...
  44. .claude/settings.json generated: office hooks + marketplace plugins
  45. company/charter.md, org-chart.md, operating-rules.md generated
  46. company/goals.md, decisions.md, approvals.md, board.md created once, then yours
  47. handoffs/ one file per finished ticket
  48. ```
  49. Rebuilds overwrite only files the factory generated (tracked in `.factory-manifest.json`). Your goals, decisions, approvals and board are never touched, and existing files that the factory did not create are skipped unless you pass `--force`.
  50. ## A company in config
  51. ```toml
  52. [company]
  53. name = "Paperplane"
  54. mission = "Turn every support ticket into a product decision for small software teams."
  55. [[roles]]
  56. use = "engineer" # start from a built-in role...
  57. model = "opus" # ...override any field
  58. owns = ["app/"]
  59. skills_add = ["security-review"] # ...or extend a list
  60. plugin_skills = ["example-skills:webapp-testing"] # skills from a plugin marketplace
  61. look = { shirt = "#3d85c6", hair_style = "spiky", accessory = "headset" } # how they look in the office
  62. [[roles]]
  63. id = "triager" # or define a role from scratch
  64. title = "Issue Triager"
  65. description = "Reads new issues, reproduces bugs, drafts replies. Use for any incoming issue."
  66. mission = "No issue waits more than a day for a useful first response."
  67. skills = ["issue-triage"]
  68. [[office.rooms]]
  69. id = "build"
  70. title = "Build"
  71. roles = ["engineer", "triager"]
  72. ```
  73. Everything is optional except a name, a mission and at least one role. Full reference: [docs/config.md](docs/config.md).
  74. ## Built in
  75. **Roles (10):** product-manager, tech-lead, engineer, qa-engineer, designer, market-researcher, customer-researcher, growth-marketer, sales-dev, finance-ops.
  76. **Skills (18)**, each a focused, opinionated procedure:
  77. | Build | Discover | Grow | Run |
  78. |---|---|---|---|
  79. | code-change, code-review, debugging, test-plan, security-review, adr-writing, release-notes | spec-writing, customer-interview, competitor-research, pricing-research, ux-review | content-writing, launch-checklist, outreach-drafting, issue-triage | metrics-report, decision-memo |
  80. **Marketplace skills, on by default:** Anthropic's [`document-skills`](https://github.com/anthropics/skills) (xlsx, docx, pptx, pdf) and `example-skills` (frontend-design, webapp-testing, doc-coauthoring, skill-creator, mcp-builder, ...). Add any Claude Code plugin marketplace with two lines of config. See [docs/skills.md](docs/skills.md).
  81. **Workflows:** `/kickoff <goal>`, `/standup`, `/approvals`, `/weekly-review`, `/hire <role>`, `/setup-board`.
  82. **Examples:** `company-factory list examples`
  83. | Example | Shows |
  84. |---|---|
  85. | `starter` | a blank 5-role product company with placeholders |
  86. | `saas` | an 8-role B2B SaaS startup with custom rooms and looks |
  87. | `open-source` | maintainers of an OSS project: inline custom roles, a custom `/triage` workflow, custom gates |
  88. | `content-studio` | a newsletter and video studio, to show a "company" does not have to write code |
  89. ## The office
  90. `company-factory office <dir>` serves a live view at `http://127.0.0.1:4477`:
  91. - **Rooms and people** come from `company.toml`. Each role has a stable look unless you set one.
  92. - **Activity** streams from Claude Code hooks. When the Chief of Staff delegates, a ticket flies to a desk, the monitor lights up, and speech bubbles show the current step (`editing app/export.py`, `$ run tests`). When the work is done, the agent walks the handoff to the shelf. Built-in subagents such as Explore show up as guests.
  93. - **The board** shows a kanban wall and lanes, read from `company/board.md` or from [Taskboard](docs/taskboard.md).
  94. - **Needs you:** pending approvals pile up in the founder's inbox, and a bell rings when Claude is waiting on you.
  95. - Day and night themes, and edits to `company.toml` show up without a restart.
  96. Privacy and security: the hook records only the event, the agent, the tool and a few-word label. Prompts, file contents and tool output are never recorded. The server only reads: it cannot change files or run commands, it listens on localhost only, and it checks the `Host` header so other websites cannot read it. Details: [docs/office.md](docs/office.md).
  97. ## Taskboard
  98. Tickets live in [Taskboard](https://github.com/tcarac/taskboard), a local kanban board with an MCP server (a prerequisite; see above). Set `[taskboard] enabled = false` to use a plain `company/board.md` instead.
  99. ```bash
  100. brew tap tcarac/taskboard && brew install taskboard
  101. taskboard start # http://localhost:3010
  102. ```
  103. ```toml
  104. [taskboard]
  105. enabled = true
  106. project = "Acme HQ"
  107. prefix = "ACME"
  108. ```
  109. `build` registers the Taskboard MCP server in the company's `.mcp.json`. In Claude Code, run `/setup-board` once: it creates the project, your lanes and one agent per role (it is idempotent). The Chief of Staff then creates and moves tickets through MCP, and the office reads the board live. See [docs/taskboard.md](docs/taskboard.md).
  110. ## Commands
  111. | Command | Does |
  112. |---|---|
  113. | `demo [--example NAME]` | build a sample company in a temp folder and open its office with scripted activity |
  114. | `init <dir> [--example NAME]` | copy an example's config and plug-ins (never overwrites) |
  115. | `validate <dir>` | check the config and report every problem at once |
  116. | `doctor [<dir>]` | check prerequisites: Node, Claude Code, Taskboard (installed, running, set up), plugins, hooks |
  117. | `build <dir> [--dry-run] [--force]` | generate or update the workspace |
  118. | `plugins <dir> [--install]` | print or run the commands that install the company's marketplace plugins |
  119. | `office <dir> [--port N] [--open] [--demo]` | serve the live office |
  120. | `list roles\|skills\|workflows\|examples [--dir <company>]` | show what can be plugged in |
  121. | `office-hooks` | print the hooks block, for merging into your own `.claude/settings.json` |
  122. ## FAQ
  123. **Does this run agents by itself?** No. Claude Code runs them, with your account and your permission settings. `company-factory` writes the workspace, and the office watches it.
  124. **Will agents send emails or push code?** The operating rules make external communication, publishing, money, legal, irreversible actions and direction changes approval gates. Agents prepare that work and add a request to `company/approvals.md`. Your Claude Code permission settings still apply on top.
  125. **Can I use my own roles and skills?** Yes. Put them in `<company>/custom/` (they can override a built-in with the same id), or add them to the library and send a PR.
  126. **Windows?** CI runs on Windows. The hook runs with `node`, so Node must be on your PATH. Reports welcome.
  127. ## Contributing
  128. New roles, skills, examples and office art are all welcome. See [CONTRIBUTING.md](CONTRIBUTING.md). Run the tests with `npm test`.
  129. ## License
  130. MIT. The office art is original and drawn in code. The UI bundles [Preact](https://preactjs.com) (MIT) and [htm](https://github.com/developit/htm) (Apache-2.0); their license notices ship in `dist/web/app.js`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.