speccrew 0.6.8 → 0.6.9

package/.speccrew/agents/speccrew-product-manager.md

@@ -1,7 +1,7 @@
 ---
 name: speccrew-product-manager
 description: SpecCrew Product Manager. Analyzes user requirements, performs complexity assessment to route between simple (single PRD) and complex (Master-Sub PRD) workflows, reads business knowledge and domain specifications, writes structured PRD documents, and waits for manual confirmation before transitioning to speccrew-planner. Handles both lightweight requirements (1-2 modules, ≤5 features) and complex multi-module requirements (3+ modules, 6+ features). Trigger scenarios: user describes new feature requirements, feature changes, or bug fix requests.
-tools: Read, Write, Glob, Grep, Bash
+tools: Read, Write, Glob, Grep, Bash, Agent
 ---
 
 # Role Positioning
@@ -246,6 +246,7 @@ After IDE detection, compute and store all absolute paths as workflow context va
 > - DO NOT create `entry-dirs-*.json` files manually via file write/create operations
 > - DO NOT create `sync-state` directories under `knowledges/techs/` — sync-state ONLY exists under `knowledges/base/`
 > - ALL features and entry-dirs files MUST be generated by scripts executed via `run_in_terminal`
+> - ⛔ PM Agent MUST NOT execute knowledge-base scripts (generate-inventory.js, etc.) via Bash — ALL script execution MUST happen inside Worker Agents
 >
 > **Output Path Rule:**
 > - Features files: `{sync_state_bizs_dir}/features-{platform}.json`
@@ -267,6 +268,18 @@ After IDE detection, compute and store all absolute paths as workflow context va
 
 > **MANDATORY**: Dispatch Worker with the detector skill. DO NOT manually search directories or check file existence yourself.
 
+   **Agent Tool Invocation Format**:
+   ```
+   Use the Agent tool to invoke speccrew-task-worker:
+   - agent: speccrew-task-worker
+   - task: Execute speccrew-pm-knowledge-detector skill
+   - context:
+       skill: speccrew-pm-knowledge-detector
+       workspace_path: {workspace_path}
+       sync_state_bizs_dir: {sync_state_bizs_dir}
+       configs_dir: {configs_dir}
+   ```
+
 **Worker returns** a JSON status object:
 
 ```json
@@ -304,6 +317,16 @@ Feature inventory exists but detailed analysis may be incomplete.
    | `language` | Detected user language |
    | `sync_state_bizs_dir` | `{sync_state_bizs_dir}` (absolute path from Phase 0.6) |
 
+   **Agent Tool Invocation Format**:
+   ```
+   Use the Agent tool to invoke speccrew-task-worker:
+   - agent: speccrew-task-worker
+   - task: Execute speccrew-pm-module-matcher skill
+   - context:
+       skill: speccrew-pm-module-matcher
+       sync_state_bizs_dir: {sync_state_bizs_dir}
+   ```
+
 2. **Worker returns** matched modules with confidence levels
 
 3. **Present to user**:
@@ -374,6 +397,26 @@ No knowledge base exists. A lightweight feature inventory scan is triggered to d
    > **DO NOT** manually create features-*.json files — they MUST be generated by the script inside the skill.
    > **DO NOT** write any files to `knowledges/techs/*/` — output goes to `knowledges/base/sync-state/knowledge-bizs/` ONLY.
 
+   **Agent Tool Invocation Format** (you MUST follow this exact format):
+   ```
+   Use the Agent tool to invoke speccrew-task-worker:
+   - agent: speccrew-task-worker
+   - task: Execute speccrew-knowledge-bizs-init-features skill
+   - context:
+       skill: speccrew-knowledge-bizs-init-features
+       workspace_path: {workspace_path}
+       language: {language}
+       sync_state_bizs_dir: {sync_state_bizs_dir}
+       configs_dir: {configs_dir}
+       ide_skills_dir: {ide_skills_dir}
+   ```
+
+   > ⛔ **CRITICAL ENFORCEMENT**:
+   > - You MUST use the **Agent tool** to invoke `speccrew-task-worker` — this is the ONLY permitted way to execute this step
+   > - DO NOT use Bash tool to run generate-inventory.js directly — PM Agent must NOT execute knowledge scripts itself
+   > - DO NOT use Write tool to manually create features-*.json or entry-dirs-*.json
+   > - If you lack the Agent tool → STOP and REPORT ERROR to user before proceeding
+
    - Worker scans project structure to discover platforms and modules
    - Worker generates `features-*.json` files (metadata: module names, feature counts, file paths)
    - This is a **lightweight scan** — no deep analysis of module internals

package/.speccrew/agents/speccrew-task-worker.md

@@ -101,6 +101,12 @@ If the skill file is not found, report an error with the attempted paths.
 4. Strictly execute according to the workflow defined in the Skill
 5. Complete the task and output results
 
+> 🛑 **CRITICAL — Skill Execution Enforcement**:
+> - If the Skill specifies script execution via `run_in_terminal` or `Bash` → You MUST execute the script via terminal. DO NOT substitute with manual file creation.
+> - If the Skill specifies `--outputDir` or other path parameters → You MUST pass them exactly as provided in the context.
+> - If the Skill contains MANDATORY/FORBIDDEN constraints → You MUST follow them strictly.
+> - DO NOT improvise alternative execution paths. If a step fails, report the error — do not attempt workarounds.
+
 **If `skill_name` is NOT provided:**
 1. Parse `context` to understand the task requirements
 2. Execute the task directly based on context description

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "speccrew",
-  "version": "0.6.8",
+  "version": "0.6.9",
   "description": "Spec-Driven Development toolkit for AI-powered IDEs",
   "author": "charlesmu99",
   "repository": {