company-skill 4.2.0 → 4.4.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.
- package/README.md +21 -8
- package/package.json +1 -1
- package/skill/SKILL.md +21 -3
package/README.md
CHANGED
|
@@ -75,15 +75,21 @@ Every employee gets their task, previous findings, and failed approaches from th
|
|
|
75
75
|
<details>
|
|
76
76
|
<summary><strong>VERIFY</strong> — Triple quality gate blocks premature completion</summary>
|
|
77
77
|
|
|
78
|
-
**Internal Reviewer** checks each criterion in criteria.json against evidence. No evidence? Stays `false`.
|
|
78
|
+
**Internal Reviewer** checks each criterion in criteria.json against evidence. No evidence? Stays `false`. Also scans all public-facing output for unverified claims about external projects — any number, percentage, or technical detail cited from memory gets blocked until verified from source.
|
|
79
79
|
|
|
80
|
-
**Devil's Advocate** attacks anything marked as passing. "Is this actually complete or surface-level? What edge cases were missed?"
|
|
80
|
+
**Devil's Advocate** attacks anything marked as passing. "Is this actually complete or surface-level? What edge cases were missed?" For any claim about external projects: "did you actually verify this from their repo/docs, or are you guessing?"
|
|
81
81
|
|
|
82
82
|
**Elegance Enforcer** asks "Can this be simpler? Does every component justify its existence?"
|
|
83
83
|
|
|
84
84
|
All three must accept before the loop exits.
|
|
85
85
|
</details>
|
|
86
86
|
|
|
87
|
+
## External Fact Verification
|
|
88
|
+
|
|
89
|
+
Workers producing public-facing output (GitHub comments, PRs, blog posts) must verify every claim about external projects from their actual docs/source before publishing. No citing from memory. The reviewer blocks unverified external claims automatically.
|
|
90
|
+
|
|
91
|
+
**One strike rule:** if corrected by someone, respond "my bad, you're right" and stop. Never attempt a second correction with more guessed details.
|
|
92
|
+
|
|
87
93
|
## Goal Enforcement
|
|
88
94
|
|
|
89
95
|
The skill creates `criteria.json` with machine-checkable success criteria:
|
|
@@ -145,13 +151,20 @@ Override per employee: `- ML Scientist, experiments [opus]`
|
|
|
145
151
|
|
|
146
152
|
## Installed Skills
|
|
147
153
|
|
|
148
|
-
Auto-installed on first run.
|
|
154
|
+
Auto-installed on first run. Leads assign skills to workers by task type.
|
|
155
|
+
|
|
156
|
+
| Task type | Skill | Pack |
|
|
157
|
+
|-----------|-------|------|
|
|
158
|
+
| Code review | /review | gstack |
|
|
159
|
+
| Bug fix | /investigate | gstack |
|
|
160
|
+
| QA testing | /qa | gstack |
|
|
161
|
+
| Ship code | /ship | gstack |
|
|
162
|
+
| Browse/test site | /browse | gstack |
|
|
163
|
+
| Security audit | /secure-phase | trailofbits |
|
|
164
|
+
| Debug with state | /gsd-debug | GSD |
|
|
165
|
+
| Plan work | /gsd-plan-phase | GSD |
|
|
149
166
|
|
|
150
|
-
|
|
151
|
-
|------|-------------------|
|
|
152
|
-
| gstack | /review, /ship, /qa, /investigate, /browse |
|
|
153
|
-
| GSD | /gsd-plan-phase, /gsd-execute-phase, /gsd-verify-work, /gsd-debug |
|
|
154
|
-
| trailofbits | Security audit, vulnerability detection |
|
|
167
|
+
If no skill matches the task, workers use raw tools.
|
|
155
168
|
|
|
156
169
|
<details>
|
|
157
170
|
<summary>Install more skill packs</summary>
|
package/package.json
CHANGED
package/skill/SKILL.md
CHANGED
|
@@ -88,6 +88,10 @@ If a lead realizes an idle employee is needed after all: add them to active rost
|
|
|
88
88
|
|
|
89
89
|
Each worker gets: their task, their previous findings file, failed approaches from playbook.
|
|
90
90
|
|
|
91
|
+
If a skill was assigned (see Skill Routing table), invoke it via the Skill tool FIRST before doing anything else.
|
|
92
|
+
|
|
93
|
+
**EXTERNAL FACT RULE (highest priority):** Before writing ANY public-facing output (GitHub comments, PR descriptions, emails, blog posts) that states a specific fact about an external project (version numbers, API details, feature claims, architecture, block formats), the worker MUST verify it first using WebFetch or `gh api` to read the project's actual docs/source/README. If it cannot verify, it must say "not sure" instead of guessing. NEVER cite external numbers from memory. ONE STRIKE: if corrected, respond "my bad, you're right" and stop — never attempt a second correction with more guessed details.
|
|
94
|
+
|
|
91
95
|
Every finding MUST have:
|
|
92
96
|
```
|
|
93
97
|
FINDING: what
|
|
@@ -102,8 +106,9 @@ Novel ideas (new techniques, hypotheses, untested approaches) use "NOVEL - needs
|
|
|
102
106
|
Internal Reviewer reads criteria.json + all findings. For each criterion:
|
|
103
107
|
- Evidence exists with source? Set passes: true in criteria.json
|
|
104
108
|
- No evidence or source missing? Keep passes: false
|
|
109
|
+
- **External fact check:** Scan every outgoing comment/email/blog for claims about external projects (numbers, percentages, technical details, feature comparisons). If any claim wasn't verified from the actual source (repo, docs, README), BLOCK the output and send the worker back to verify. Memory-based claims about external projects = automatic rejection.
|
|
105
110
|
|
|
106
|
-
Devil's Advocate attacks anything marked as passing.
|
|
111
|
+
Devil's Advocate attacks anything marked as passing. **Specifically for external claims:** ask "did you actually verify this from their repo/docs, or are you guessing?" for every statement about a competitor or external project.
|
|
107
112
|
|
|
108
113
|
Print as plain text (NOT Bash):
|
|
109
114
|
|
|
@@ -142,9 +147,22 @@ CEO updates COMPANY.md: tag `[inactive]` on zero-contribution roles, `[priority]
|
|
|
142
147
|
CEO, CTO, Internal Reviewer, User Advocate, Devil's Advocate, Elegance Enforcer.
|
|
143
148
|
Deduplicated if user defines them in COMPANY.md.
|
|
144
149
|
|
|
145
|
-
##
|
|
150
|
+
## Skill Routing
|
|
151
|
+
|
|
152
|
+
Leads MUST assign a skill when the task matches. Workers MUST invoke it via the Skill tool.
|
|
153
|
+
|
|
154
|
+
| Task type | Skill | When |
|
|
155
|
+
|-----------|-------|------|
|
|
156
|
+
| Code review | /review | Any PR or diff needs review before merging |
|
|
157
|
+
| Bug fix | /investigate | Root cause unknown, need systematic debugging |
|
|
158
|
+
| QA testing | /qa | Test a web app, find and fix bugs |
|
|
159
|
+
| Ship code | /ship | Create PR, run tests, push |
|
|
160
|
+
| Security audit | /secure-phase | Check for vulnerabilities in code |
|
|
161
|
+
| Debug with state | /gsd-debug | Complex bug needing persistent debug session |
|
|
162
|
+
| Plan work | /gsd-plan-phase | Break complex task into steps |
|
|
163
|
+
| Browse/test site | /browse | Navigate URLs, check page state, screenshots |
|
|
146
164
|
|
|
147
|
-
|
|
165
|
+
If no skill matches, workers use raw tools (Read, Write, Bash, etc.).
|
|
148
166
|
|
|
149
167
|
## Stop Hook
|
|
150
168
|
|