company-skill 4.1.0 → 4.3.0

package/README.md

@@ -2,6 +2,8 @@
 
 [![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)
 
+> *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.*
+
 **Define your team in markdown. Give it a goal. Walk away.**
 
 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.
@@ -143,13 +145,20 @@ Override per employee: `- ML Scientist, experiments [opus]`
 
 ## Installed Skills
 
-Auto-installed on first run. When installed, employees MUST use them.
+Auto-installed on first run. Leads assign skills to workers by task type.
+
+| Task type | Skill | Pack |
+|-----------|-------|------|
+| Code review | /review | gstack |
+| Bug fix | /investigate | gstack |
+| QA testing | /qa | gstack |
+| Ship code | /ship | gstack |
+| Browse/test site | /browse | gstack |
+| Security audit | /secure-phase | trailofbits |
+| Debug with state | /gsd-debug | GSD |
+| Plan work | /gsd-plan-phase | GSD |
 
-| Pack | What employees get |
-|------|-------------------|
-| gstack | /review, /ship, /qa, /investigate, /browse |
-| GSD | /gsd-plan-phase, /gsd-execute-phase, /gsd-verify-work, /gsd-debug |
-| trailofbits | Security audit, vulnerability detection |
+If no skill matches the task, workers use raw tools.
 
 <details>
 <summary>Install more skill packs</summary>
@@ -175,6 +184,27 @@ Auto-installed on first run. When installed, employees MUST use them.
   {dept}/              Per-employee findings (persist across sessions)
 ```
 
+## Design Choices
+
+Three principles behind the skill:
+
+- **One file to define the team.** COMPANY.md is the only thing you write. Everything else — delegation, task routing, quality checks — is automatic.
+- **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.
+- **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.
+
+## Project Structure
+
+```
+COMPANY.md           Your team definition (the only file you edit)
+skill/SKILL.md       The skill logic (THINK > EXECUTE > VERIFY loop)
+agents/              Subagent definitions (lead, worker, reviewer, critic, digest)
+hooks/               Stop guard, session restore, precompact
+commands/            run.md, resume.md, status.md
+examples/            Sample team configurations
+install.sh           Curl-based installer
+bin/install.js       npx installer
+```
+
 ## Examples
 
 | File | Team |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "company-skill",
-  "version": "4.1.0",
+  "version": "4.3.0",
   "description": "Goal-driven multi-employee company for Claude Code. Give it a goal, it runs until done.",
   "bin": {
     "company-skill": "./bin/install.js"

package/skill/SKILL.md

@@ -88,6 +88,8 @@ If a lead realizes an idle employee is needed after all: add them to active rost
 
 Each worker gets: their task, their previous findings file, failed approaches from playbook.
 
+If a skill was assigned (see Skill Routing table), invoke it via the Skill tool FIRST before doing anything else.
+
 Every finding MUST have:
 ```
 FINDING: what
@@ -142,9 +144,22 @@ CEO updates COMPANY.md: tag `[inactive]` on zero-contribution roles, `[priority]
 CEO, CTO, Internal Reviewer, User Advocate, Devil's Advocate, Elegance Enforcer.
 Deduplicated if user defines them in COMPANY.md.
 
-## Skills
+## Skill Routing
+
+Leads MUST assign a skill when the task matches. Workers MUST invoke it via the Skill tool.
+
+| Task type | Skill | When |
+|-----------|-------|------|
+| Code review | /review | Any PR or diff needs review before merging |
+| Bug fix | /investigate | Root cause unknown, need systematic debugging |
+| QA testing | /qa | Test a web app, find and fix bugs |
+| Ship code | /ship | Create PR, run tests, push |
+| Security audit | /secure-phase | Check for vulnerabilities in code |
+| Debug with state | /gsd-debug | Complex bug needing persistent debug session |
+| Plan work | /gsd-plan-phase | Break complex task into steps |
+| Browse/test site | /browse | Navigate URLs, check page state, screenshots |
 
-When installed: MUST use /review for code review, /investigate for bugs, /qa for testing, /ship for PRs. Skills are installed in the Preamble.
+If no skill matches, workers use raw tools (Read, Write, Bash, etc.).
 
 ## Stop Hook