clearctx 3.0.0 → 3.1.0

package/README.md

@@ -1004,3 +1004,4 @@ clearctx team-replay pre-work --overrides overrides.json
 ## License
 
 MIT
+

package/bin/setup.js

@@ -178,6 +178,33 @@ This shows which workers actually read the conventions. If a worker is missing,
 
 NEVER trust a worker's self-reported completion — verify the artifact exists yourself.
 
+### Rule 8: Use expertise skills for domain work
+
+When spawning workers, assign relevant expertise skills to improve output quality:
+
+1. Call \`skill_detect\` with the task description to auto-match skills
+2. Pass matched skills to \`team_spawn\` via the \`skills\` parameter:
+   \`\`\`
+   team_spawn({
+     name: "db-dev",
+     role: "database",
+     skills: ["postgresql"],
+     prompt: "Create the database schema..."
+   })
+   \`\`\`
+3. Override auto-detection with explicit skills when you know better
+4. Workers with skills produce higher-quality, convention-compliant output
+5. Available skills: postgresql, nodejs-backend, react-frontend, testing-qa, api-design, devops, security, typescript
+
+**Role-based fallback:** If you don't specify skills but provide a role, the system auto-detects relevant skills:
+- database → postgresql
+- backend → nodejs-backend, api-design
+- frontend → react-frontend
+- QA/testing → testing-qa
+- devops → devops
+- security → security
+- fullstack → nodejs-backend, react-frontend, typescript
+
 ## Auto-Behaviors (v2.7.0)
 
 These happen automatically — no action needed from you or the workers:
@@ -186,8 +213,9 @@ These happen automatically — no action needed from you or the workers:
 - **Inbox enforcement**: Workers are blocked from using artifact/contract tools until they call \`team_check_inbox\`
 - **File ownership tracking**: \`artifact_publish\` auto-registers file ownership from \`files\`/\`filesCreated\`/\`filesModified\` arrays in artifact data
 - **Convention completeness check**: \`phase_gate\` warns if \`shared-conventions\` artifact is missing or has incomplete fields
+- **Skills System**: When you provide a \`role\` to \`team_spawn\` without explicit \`skills\`, the system auto-detects relevant expertise skills based on the role (e.g., "database" → postgresql, "backend" → nodejs-backend + api-design). You can override this by passing explicit \`skills\` array.
 
-## Quick Reference (68 tools)
+## Quick Reference (71 tools)
 
 | You want to... | Use this tool |
 |----------------|---------------|
@@ -202,6 +230,10 @@ These happen automatically — no action needed from you or the workers:
 | Check who read an artifact | \`artifact_readers\` |
 | Check file ownership (Rule 6) | \`check_file_owner\` |
 | Register file ownership | \`register_files\` |
+| Auto-detect skills for a task | \`skill_detect\` |
+| List available skills | \`skill_list\` |
+| Read a skill's content | \`skill_get\` |
+| Spawn worker with skills | \`team_spawn\` with \`skills\` parameter |
 | Clean up between runs | \`team_reset\` |
 
 ### When NOT to Delegate

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clearctx",
-  "version": "3.0.0",
+  "version": "3.1.0",
   "description": "Multi-session orchestrator for Claude Code CLI — spawn, control, pause, resume, and send multiple inputs to Claude Code sessions programmatically",
   "main": "src/index.js",
   "bin": {
@@ -31,7 +31,7 @@
     "parallel-tasks",
     "workflow-automation"
   ],
-  "author": "",
+  "author": "RevanthThota55 <revanththota55@gmail.com>",
   "license": "MIT",
   "engines": {
     "node": ">=18.0.0"
@@ -39,6 +39,7 @@
   "files": [
     "src/",
     "bin/",
+    "skills/",
     "README.md",
     "CHANGELOG.md",
     "STRATEGY.md",