@thecodesaiyan/claude-dev-workflow-hook 1.0.0 → 1.0.1

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/package.json +1 -1
  2. package/src/protocol.js +7 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@thecodesaiyan/claude-dev-workflow-hook",
3
- "version": "1.0.0",
3
+ "version": "1.0.1",
4
4
  "description": "SessionStart hook that injects a structured development workflow protocol into Claude Code sessions",
5
5
  "keywords": [
6
6
  "claude",
package/src/protocol.js CHANGED
@@ -83,9 +83,13 @@ Do NOT do all work inline — delegate to Agent Teams or subagents.
83
83
 
84
84
  Before Phase 1, determine which mode to use:
85
85
 
86
- 1. Run: \`echo $CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS\`
87
- 2. If the value is \`"1"\` → **Agent Teams mode** (REQUIRED — you MUST use it).
88
- 3. Otherwise → **Subagent fallback mode** (use the \`Task\` tool).
86
+ 1. Check if Agent Teams are enabled: look for teammate-spawning capabilities in
87
+ your available tools (e.g., the ability to spawn teammates, manage a shared task
88
+ list across agents, or send messages between agents). Agent Teams are enabled
89
+ when \`CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS\` is set to \`"1"\` in the environment
90
+ or in settings.json. If you have teammate capabilities → Agent Teams are available.
91
+ 2. If Agent Teams are available → **Agent Teams mode** (REQUIRED — you MUST use it).
92
+ 3. If Agent Teams are NOT available → **Subagent fallback mode** (use the \`Task\` tool).
89
93
  4. Announce: \`[PROTOCOL Rule 4] Orchestration: Agent Teams mode\` or
90
94
  \`[PROTOCOL Rule 4] Orchestration: Subagent fallback — Agent Teams not enabled\`
91
95