company-skill 4.1.0 → 4.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +23 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -2,6 +2,8 @@
2
2
 
3
3
  [![npm](https://img.shields.io/npm/v/company-skill)](https://www.npmjs.com/package/company-skill) [![license](https://img.shields.io/npm/l/company-skill)](LICENSE) [![downloads](https://img.shields.io/npm/dw/company-skill)](https://www.npmjs.com/package/company-skill)
4
4
 
5
+ > *You don't prompt agents one at a time. You write a team in markdown, hand them a goal, and go to sleep. In the morning, STATUS.md tells you what got done, what got rejected, and what the company learned. The playbook from session 3 makes session 4 faster. By session 10, the company runs itself better than you could direct it manually.*
6
+
5
7
  **Define your team in markdown. Give it a goal. Walk away.**
6
8
 
7
9
  A Claude Code skill that runs your entire company — CEO delegates, departments execute in parallel, built-in reviewers verify — and doesn't stop until the goal is done.
@@ -175,6 +177,27 @@ Auto-installed on first run. When installed, employees MUST use them.
175
177
  {dept}/ Per-employee findings (persist across sessions)
176
178
  ```
177
179
 
180
+ ## Design Choices
181
+
182
+ Three principles behind the skill:
183
+
184
+ - **One file to define the team.** COMPANY.md is the only thing you write. Everything else — delegation, task routing, quality checks — is automatic.
185
+ - **No iteration limit.** The loop runs until criteria.json says done. Not 3 cycles. Not 5. Until the Reviewer and Devil's Advocate both accept.
186
+ - **Self-improvement over configuration.** Instead of tuning prompts, the company learns from its own failures. The playbook accumulates across sessions. Roles get tagged `[priority]` or `[inactive]` based on performance. The system gets better by running, not by tweaking.
187
+
188
+ ## Project Structure
189
+
190
+ ```
191
+ COMPANY.md Your team definition (the only file you edit)
192
+ skill/SKILL.md The skill logic (THINK > EXECUTE > VERIFY loop)
193
+ agents/ Subagent definitions (lead, worker, reviewer, critic, digest)
194
+ hooks/ Stop guard, session restore, precompact
195
+ commands/ run.md, resume.md, status.md
196
+ examples/ Sample team configurations
197
+ install.sh Curl-based installer
198
+ bin/install.js npx installer
199
+ ```
200
+
178
201
  ## Examples
179
202
 
180
203
  | File | Team |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "company-skill",
3
- "version": "4.1.0",
3
+ "version": "4.2.0",
4
4
  "description": "Goal-driven multi-employee company for Claude Code. Give it a goal, it runs until done.",
5
5
  "bin": {
6
6
  "company-skill": "./bin/install.js"