specweave 1.0.260 → 1.0.262

package/plugins/specweave/skills/plan/SKILL.md

@@ -77,6 +77,43 @@ Generate `plan.md` and `tasks.md` for an increment using Architect Agent and tes
    - PLANNING → ACTIVE transition (tasks.md now exists)
    - Update lastUpdated timestamp
 
+6. **Execution Strategy Recommendation** (MANDATORY):
+   After generating tasks.md, analyze complexity and output a recommendation:
+
+   **6a. Count pending tasks** in the generated tasks.md (count `[ ]` markers)
+
+   **6b. Detect domains** from file paths and task descriptions:
+   - Frontend: `src/components/`, `src/pages/`, `src/hooks/`, `src/styles/`, `.tsx`, `.css`, React/Vue/Angular keywords
+   - Backend: `src/api/`, `src/services/`, `src/middleware/`, `src/routes/`, Express/Fastify/NestJS keywords
+   - Database: `prisma/`, `src/db/`, `migrations/`, `schema`, SQL/Prisma keywords
+   - DevOps: `Dockerfile`, `.github/`, `k8s/`, `terraform/`, CI/CD keywords
+   - Testing: `tests/`, `e2e/`, `.test.`, `.spec.`, test framework keywords
+   - Security: `src/auth/`, authentication, authorization keywords
+   - Mobile: `ios/`, `android/`, React Native keywords
+
+   **6c. Apply execution strategy matrix** and output:
+   ```
+   EXECUTION STRATEGY
+   ══════════════════════════════════════════
+   Tasks: [N] pending | Domains: [N] ([list])
+   ──────────────────────────────────────────
+   Recommended: /sw:do        (≤8 tasks, 1 domain)
+   Recommended: /sw:auto      (9-15 tasks, 1-2 domains)
+   Recommended: /sw:team-lead (>15 tasks OR 3+ domains)
+   ══════════════════════════════════════════
+   ⚠️  /sw:team-lead uses more tokens but produces higher quality
+      through parallel domain-specialized agents.
+
+   Next: /sw:team-lead [ID] | /sw:auto [ID] | /sw:do [ID]
+   ```
+
+   Show ONLY the matching recommendation line (not all three).
+   For 3+ domains, add a stronger nudge:
+   ```
+   ⚡ This is a multi-domain feature. /sw:team-lead is strongly recommended
+      for parallel execution across [domain1], [domain2], [domain3].
+   ```
+
 ## Options
 
 - `--force`: Overwrite existing plan.md/tasks.md

package/plugins/specweave/skills/pm/phases/00-deep-interview.md

@@ -13,7 +13,7 @@ The gate instructs the LLM to **assess prompt completeness** before deciding whe
 **How it works:**
 - Gate fires on every prompt, accumulating context across messages
 - LLM evaluates technical signals (stack, integrations, auth, deployment) AND product signals (users, flows, business model)
-- If the user's prompt is comprehensive enough for the detected complexity → skip interview, proceed to `sw:increment-planner`
+- If the user's prompt is comprehensive enough for the detected complexity → skip interview, proceed to `sw:increment`
 - If gaps exist → ask 2-5 targeted questions about what's missing (NOT a full interview)
 
 **As PM skill, your role when gate is active:**
@@ -45,7 +45,7 @@ When `enforcement: "strict"` is configured, spec.md creation is BLOCKED by `inte
 
 **To track category completion:**
 
-1. **Initialize interview state** (done by increment-planner):
+1. **Initialize interview state** (done by increment skill):
    ```bash
    mkdir -p .specweave/state
    echo '{"incrementId":"XXXX-name","startedAt":"'$(date -Iseconds)'","coveredCategories":{}}' > .specweave/state/interview-XXXX-name.json

package/plugins/specweave/skills/progress-sync/SKILL.md

@@ -70,9 +70,7 @@ tasks.md → spec.md ACs → living docs → AUTO-CREATE external issues → syn
 
 ### ❌ Don't use when:
 
-1. **Only want to sync ACs**: Use `/sw:sync-acs` instead (faster, more targeted)
-2. **Only want to sync docs**: Use `/sw:sync-specs` instead
-3. **Only want to sync GitHub (issue already exists)**: Use `/sw-github:sync` instead
+1. **Only want to sync GitHub (issue already exists)**: Use `/sw-github:sync` instead
 4. **Increment not started**: No tasks to sync yet
 5. **Don't want auto-create**: Use `--no-create` flag or manual commands
 
@@ -236,15 +234,12 @@ Run without --dry-run to execute sync.
 
 | Command | Scope | Auto-Create? | When to Use |
 |---------|-------|--------------|-------------|
-| `/sw:sync-acs` | Tasks → ACs only | ❌ | Quick AC update |
-| `/sw:sync-specs` | Spec → Docs only | ❌ | After spec changes |
 | `/sw-github:create` | Create GitHub issue | ✅ | Manual issue creation |
 | `/sw-github:sync` | Docs → GitHub only | ❌ | GitHub-only sync (issue must exist) |
 | `/sw:sync-progress` | **Tasks → Docs → Create → Sync** | ✅ | **Complete sync** ✅ (RECOMMENDED!) |
 
 **Rule of thumb**:
 - Need **complete sync** (just works) → Use `/sw:sync-progress` ✅
-- Need **targeted sync** → Use specific command (`sync-acs`, `sync-specs`)
 - Need **sync only** (no auto-create) → Use `/sw:sync-progress --no-create`
 
 ---
@@ -329,10 +324,7 @@ The command checks `.specweave/config.json` for:
 
 **Fix**:
 ```bash
-# Embed ACs from living docs into spec.md
-/sw:embed-acs 0053
-
-# Then retry sync
+# Manually add ACs to spec.md, then retry sync
 /sw:sync-progress 0053
 ```
 
@@ -411,10 +403,9 @@ The command checks `.specweave/config.json` for:
 ```
 Problem: Manual multi-step sync is error-prone
   1. Update spec.md ACs manually
-  2. Run /sw:sync-specs
-  3. Run /sw-github:sync
-  4. Run /sw:update-status
-  5. Check each system for correctness
+  2. Sync living docs
+  3. Sync GitHub/JIRA/ADO
+  4. Check each system for correctness
 
 Solution: Single command orchestrates all steps
   /sw:sync-progress → Does all 4 steps automatically
@@ -431,21 +422,12 @@ Solution: Single command orchestrates all steps
 
 ## Background
 
-Before this command, users had to manually:
-1. Run `/sw:sync-acs`
-2. Run `/sw:sync-specs`
-3. Run `/sw-github:sync`
-4. Run `/sw:update-status`
-
-Now: **One command does all 4 steps** ✅
+Before this command, users had to manually sync ACs, docs, and external tools separately. Now: **One command does everything** ✅
 
 ---
 
 ## Related Commands
 
-- `/sw:sync-acs` - Sync tasks → ACs only
-- `/sw:sync-specs` - Sync spec → living docs only
-- `/sw:sync-tasks` - Sync external → tasks (bidirectional)
 - `/sw-github:sync` - Sync docs → GitHub only
 - `/sw-jira:sync` - Sync docs → JIRA only
 - `/sw-ado:sync` - Sync docs → ADO only
@@ -457,7 +439,7 @@ Now: **One command does all 4 steps** ✅
 
 Ask me:
 - "How do I sync progress to GitHub?"
-- "What's the difference between sync-progress and sync-acs?"
+- "What does sync-progress do exactly?"
 - "How do I preview sync without executing?"
 - "Why did my GitHub sync fail?"
 - "When should I use --dry-run?"