specweave 0.33.4 → 0.33.6

package/plugins/specweave/commands/{specweave-do.md → do.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:do
+name: sw:do
 description: Execute increment implementation following spec and plan - hooks run after EVERY task
 ---
 
@@ -13,15 +13,15 @@ You are helping the user implement a SpecWeave increment by executing tasks from
 
 ```bash
 # Auto-resumes from last incomplete task
-/specweave:do <increment-id>
+/sw:do <increment-id>
 
 # Or let it find active increment automatically
-/specweave:do
+/sw:do
 
 # Override model selection for all tasks (advanced)
-/specweave:do <increment-id> --model haiku
-/specweave:do <increment-id> --model sonnet
-/specweave:do <increment-id> --model opus
+/sw:do <increment-id> --model haiku
+/sw:do <increment-id> --model sonnet
+/sw:do <increment-id> --model opus
 ```
 
 ## Arguments
@@ -66,31 +66,29 @@ You are helping the user implement a SpecWeave increment by executing tasks from
    TASK_COUNT=$(grep -c "^### T-" .specweave/increments/<id>/tasks.md)
    ```
 
-   **If TASK_COUNT > 8**:
+   **If TASK_COUNT > 25**:
    ```
-   ❌ TASK COUNT EXCEEDS LIMIT
+   ⚠️ TASK COUNT EXCEEDS SOFT LIMIT
 
-   This increment has X tasks (maximum allowed: 8)
+   This increment has X tasks (soft limit: 25)
 
-   >8 tasks = context explosion = CRASH (per CLAUDE.md rules)
+   >25 tasks = consider splitting for maintainability (per CLAUDE.md rules)
 
-   💡 REQUIRED ACTION: Split this increment into smaller chunks:
+   💡 RECOMMENDED: Split this increment OR execute phase-by-phase:
 
+   Option A - Split into separate increments:
    Pattern: 0116-feature/ → Split into:
-     • 0116-feature-part1/ (T-001 to T-004)
-     • 0117-feature-part2/ (T-005 to T-008)
-     • 0118-feature-part3/ (T-009 to T-012)
+     • 0116-feature-phase1/ (T-001 to T-008)
+     • 0117-feature-phase2/ (T-009 to T-016)
+     • 0118-feature-phase3/ (T-017 to T-025)
 
-   Commands:
-     1. Create new increment folders manually
-     2. Split tasks.md into 4-task chunks
-     3. Update spec.md to reference correct tasks
-     4. Run /specweave:do on each part sequentially
+   Option B - Phase-by-phase execution (recommended for 15-25 tasks):
+     Execute Phase 1 → validate → continue to Phase 2 → ...
 
-   ⚠️ DO NOT PROCEED - splitting is MANDATORY for stability!
+   User choice required to proceed.
    ```
 
-   **If TASK_COUNT <= 8**: Proceed to next step
+   **If TASK_COUNT <= 25**: Proceed to next step
 
 5. **🚨 CRITICAL: Validate AC Presence (v0.24.0+)**:
 
@@ -116,12 +114,12 @@ You are helping the user implement a SpecWeave increment by executing tasks from
       • spec.md contains 0 ACs (expected 39)
       • ACs are REQUIRED for task-AC sync to work
 
-   💡 Fix: Run /specweave:embed-acs <increment-id>
+   💡 Fix: Run /sw:embed-acs <increment-id>
    ```
 
    **What to Do After Validation**:
    - ✅ **If validation passes**: Proceed to Step 2
-   - ❌ **If validation fails**: Show error, run `/specweave:embed-acs`, then retry
+   - ❌ **If validation fails**: Show error, run `/sw:embed-acs`, then retry
    - **DO NOT PROCEED** without ACs in spec.md (hooks will fail!)
 
    **Why This Matters** (ADR-0064):
@@ -266,7 +264,7 @@ If already "in-progress", keep existing metadata.
      - New features
 
    **Step D: Continue to next task**:
-   - Do NOT call `/specweave:sync-docs` yet (wait until all tasks complete)
+   - Do NOT call `/sw:sync-docs` yet (wait until all tasks complete)
    - Move to next incomplete task
 
 **Example task execution**:
@@ -418,10 +416,10 @@ Up next:
 📝 Now syncing implementation learnings to living docs...
 ```
 
-**CRITICAL: Now run `/specweave:sync-docs update` to sync to living docs**:
+**CRITICAL: Now run `/sw:sync-docs update` to sync to living docs**:
 
 ```bash
-/specweave:sync-docs update
+/sw:sync-docs update
 ```
 
 This will:
@@ -431,15 +429,15 @@ This will:
 - Update feature lists with completed features
 - May prompt for conflict resolution if needed
 
-**After `/specweave:sync-docs update` completes**:
+**After `/sw:sync-docs update` completes**:
 
 ```
 ✅ Living documentation synchronized!
 
 Next steps:
 1. Run full test suite: npm test
-2. Validate increment: /specweave:validate 0001 --quality
-3. Close increment: /specweave:done 0001 (PM validates before closing)
+2. Validate increment: /sw:validate 0001 --quality
+3. Close increment: /sw:done 0001 (PM validates before closing)
 ```
 
 ---
@@ -503,7 +501,7 @@ After each task, Claude should manually update:
 - **README.md**: User-facing features, installation, usage, API changes
 - **CHANGELOG.md**: Public API changes, breaking changes, new features
 
-**Living docs sync** (via `/specweave:sync-docs update`):
+**Living docs sync** (via `/sw:sync-docs update`):
 - Only after ALL tasks complete
 - Updates `.specweave/docs/` with implementation learnings
 - Updates ADRs from Proposed → Accepted
@@ -516,7 +514,7 @@ After each task, Claude should manually update:
 ### Example 1: Execute Complete Increment
 
 ```bash
-/specweave:do 0001
+/sw:do 0001
 ```
 
 **Output**:
@@ -536,13 +534,13 @@ Task T001: Create User model
 
 🎉 All tasks completed (42/42)
 
-Next: /specweave:validate 0001 --quality
+Next: /sw:validate 0001 --quality
 ```
 
 ### Example 2: Execute with Blocker
 
 ```bash
-/specweave:do 0002
+/sw:do 0002
 ```
 
 **Output**:
@@ -565,7 +563,7 @@ Your choice? [A/B/C]: _
 ### Example 3: Execute with Test Failure
 
 ```bash
-/specweave:do 0003
+/sw:do 0003
 ```
 
 **Output**:
@@ -602,7 +600,7 @@ Available increments:
   • 0002-core-enhancements (planned)
   • 0003-payment-processing (in-progress)
 
-Usage: /specweave:do <increment-id>
+Usage: /sw:do <increment-id>
 ```
 
 ### Increment Not Planned
@@ -611,7 +609,7 @@ Usage: /specweave:do <increment-id>
 
 Increment must be "planned" before execution.
 
-Run: /specweave:increment "User authentication" to plan this increment first.
+Run: /sw:increment "User authentication" to plan this increment first.
 ```
 
 ### No Tasks to Execute
@@ -623,7 +621,7 @@ This usually means:
   2. Tasks.md is empty or missing
 
 Options:
-  1. Re-plan increment: /specweave:increment 0001 (regenerate tasks)
+  1. Re-plan increment: /sw:increment 0001 (regenerate tasks)
   2. Add tasks manually: Edit .specweave/increments/0001-name/tasks.md
 ```
 
@@ -662,6 +660,6 @@ Options:
 
 ---
 
-**Important**: This command is designed for continuous execution. It's normal to run `/specweave:do` and let it execute multiple tasks sequentially with documentation updates after each one.
+**Important**: This command is designed for continuous execution. It's normal to run `/sw:do` and let it execute multiple tasks sequentially with documentation updates after each one.
 
-**Best Practice**: Always run `/specweave:validate 0001 --quality` after execution to ensure quality before closing with `/specweave:done`.
+**Best Practice**: Always run `/sw:validate 0001 --quality` after execution to ensure quality before closing with `/sw:done`.

package/plugins/specweave/commands/{specweave-done.md → done.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:done
+name: sw:done
 description: Close increment with PM validation - checks tasks, tests, and docs before closing
 ---
 
@@ -18,7 +18,7 @@ You are acting as the Product Manager to validate increment completion before cl
 ## Usage
 
 ```bash
-/specweave:done <increment-id>
+/sw:done <increment-id>
 ```
 
 ## Arguments
@@ -125,7 +125,7 @@ if (!validation.isValid) {
   console.error('');
   validation.errors.forEach(err => console.error(`  • ${err}`));
   console.error('');
-  console.error('Fix these issues before running /specweave:done again');
+  console.error('Fix these issues before running /sw:done again');
   process.exit(1);
 }
 ```
@@ -139,7 +139,7 @@ if (!validation.isValid) {
   • 4 ACs uncovered by tasks (NEW - v0.23.0)
   • 2 orphan tasks detected (NEW - v0.23.0)
 
-Fix these issues before running /specweave:done again
+Fix these issues before running /sw:done again
 ```
 
 **Example validation output** (PASS):
@@ -217,7 +217,7 @@ if (coverageReport.uncoveredACs.length > 0) {
     `All ACs MUST have at least one implementing task.\n` +
     `Create tasks with **Satisfies ACs** field linking to these ACs.\n` +
     `\n` +
-    `Run: /specweave:validate ${incrementId} to see detailed coverage report.`
+    `Run: /sw:validate ${incrementId} to see detailed coverage report.`
   );
 }
 
@@ -231,7 +231,7 @@ if (coverageReport.orphanTasks.length > 0) {
     `All tasks MUST have **Satisfies ACs** field linking to acceptance criteria.\n` +
     `Add AC references to these tasks.\n` +
     `\n` +
-    `Run: /specweave:validate ${incrementId} to see detailed validation report.`
+    `Run: /sw:validate ${incrementId} to see detailed validation report.`
   );
 }
 ```
@@ -545,7 +545,7 @@ Closing increment 0001-user-authentication...
 - Prevents desyncs between metadata.json and spec.md
 - Ensures status line shows correct increment count
 - Maintains source-of-truth discipline
-- No need to manually run `/specweave:sync-status`
+- No need to manually run `/sw:sync-status`
 
 **What gets synced**:
 1. spec.md YAML frontmatter `status` field → `completed`
@@ -554,7 +554,7 @@ Closing increment 0001-user-authentication...
 **If you still see desync after closure**:
 ```bash
 # Manual fix (should rarely be needed)
-/specweave:sync-status --fix
+/sw:sync-status --fix
 ```
 
 **CRITICAL**: After increment closes, automatically perform these syncs:
@@ -576,7 +576,7 @@ const syncEnabled = config.hooks?.post_increment_done?.sync_to_github_project ==
 
 2. **Sync to GitHub Project**:
    ```bash
-   /specweave-github:sync-spec <spec-file>
+   /sw-github:sync-spec <spec-file>
    ```
 
 3. **Report result**:
@@ -696,7 +696,7 @@ const syncEnabled = config.hooks?.post_increment_done?.sync_to_github_project ==
    Completed: 2025-12-07
    Duration: 1 day
 
-   🔗 Closed automatically by `/specweave:done`
+   🔗 Closed automatically by `/sw:done`
    EOF
    )"
    ```
@@ -924,7 +924,7 @@ Status Sync:
 
   1. Create PR: git push && gh pr create
   2. Deploy to staging: npm run deploy:staging
-  3. Create new increment: /specweave:increment "Next feature"
+  3. Create new increment: /sw:increment "Next feature"
 ```
 
 #### Scenario B: One or More Gates Fail ❌
@@ -956,7 +956,7 @@ Action Plan:
   2. Complete T008 (JWT validation) - 3h
   3. Update CLAUDE.md - 30m
   4. Update README.md - 1h
-  5. Re-run /specweave:done 0001 for validation
+  5. Re-run /sw:done 0001 for validation
 
 Increment remains: in-progress
 
@@ -973,7 +973,7 @@ Increment remains: in-progress
 
      See PM validation report for details."
 
-Try again after fixing blockers: /specweave:done 0001
+Try again after fixing blockers: /sw:done 0001
 ```
 
 ### Step 5.25: Sync Living Docs (MANDATORY - v0.33.0+)
@@ -987,7 +987,7 @@ This ensures living docs are up-to-date with completed increment status.
 You MUST invoke the sync-specs command using the SlashCommand tool:
 
 ```
-SlashCommand(command: "/specweave:sync-specs {increment-id}")
+SlashCommand(command: "/sw:sync-specs {increment-id}")
 ```
 
 **DO NOT** just mention the command in output - you MUST actually execute it!
@@ -1027,7 +1027,7 @@ SlashCommand(command: "/specweave:sync-specs {increment-id}")
 
 1. **Invoke QA command automatically**:
    ```bash
-   /specweave:qa ${incrementId}
+   /sw:qa ${incrementId}
    ```
 
 2. **Quality assessment evaluates 7 dimensions**:
@@ -1192,7 +1192,7 @@ Closing increment 0001-user-authentication...
 ### Example 1: Successful Closure
 
 ```bash
-/specweave:done 0001
+/sw:done 0001
 ```
 
 **Output**:
@@ -1224,13 +1224,13 @@ Quality Gate Decision: ✅ PASS
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Next: /specweave:increment "Next feature"
+Next: /sw:increment "Next feature"
 ```
 
 ### Example 2: Blocked by Failing Tests
 
 ```bash
-/specweave:done 0002
+/sw:done 0002
 ```
 
 **Output**:
@@ -1251,7 +1251,7 @@ Increment remains: in-progress
 ### Example 3: Blocked by Outdated Docs
 
 ```bash
-/specweave:done 0003
+/sw:done 0003
 ```
 
 **Output**:
@@ -1274,7 +1274,7 @@ Increment remains: in-progress
 ### Example 4: Scope Creep - Transfer to Next Increment
 
 ```bash
-/specweave:done 0004
+/sw:done 0004
 ```
 
 **Output**:
@@ -1308,7 +1308,7 @@ Available increments:
   • 0002-core-enhancements (in-progress)
   • 0003-payment-processing (planned)
 
-Usage: /specweave:done <increment-id>
+Usage: /sw:done <increment-id>
 ```
 
 ### Increment Not In-Progress
@@ -1317,7 +1317,7 @@ Usage: /specweave:done <increment-id>
 
 Increment must be "in-progress" before closing.
 
-Run: /specweave:do 0001 to start implementation first.
+Run: /sw:do 0001 to start implementation first.
 ```
 
 ### Major Blockers Found
@@ -1373,7 +1373,7 @@ All PM validation settings use sensible defaults:
 
 **Important**: This command represents PM validation and MUST NOT be bypassed. All 3 gates (tasks, tests, docs) must pass before increment can close.
 
-**Best Practice**: Always run `/specweave:validate 0001 --quality` before `/specweave:done 0001` to catch issues early.
+**Best Practice**: Always run `/sw:validate 0001 --quality` before `/sw:done 0001` to catch issues early.
 
 **PM Role**: The PM agent acts as the final quality gate, ensuring:
 - ✅ Business value delivered (tasks complete)

package/plugins/specweave/commands/{specweave-embed-acs.md → embed-acs.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:embed-acs
+name: sw:embed-acs
 description: Auto-embed Acceptance Criteria from living docs into increment spec.md for hook compatibility
 ---
 
@@ -18,7 +18,7 @@ You are helping the user embed Acceptance Criteria from living documentation int
 ## Usage
 
 ```bash
-/specweave:embed-acs <increment-id>
+/sw:embed-acs <increment-id>
 ```
 
 ## Arguments
@@ -30,7 +30,7 @@ You are helping the user embed Acceptance Criteria from living documentation int
 ### Step 1: Parse and Validate Arguments
 
 1. **Extract increment ID**:
-   - Parse from command: `/specweave:embed-acs 0050` → "0050"
+   - Parse from command: `/sw:embed-acs 0050` → "0050"
    - Normalize to 4-digit format: "0050"
    - Support formats: "50", "0050", "0050-feature-name"
 
@@ -47,7 +47,7 @@ Available increments:
   • 0048-external-tool-import-enhancement
   • 0049-cli-first-init-flow
 
-Usage: /specweave:embed-acs <increment-id>
+Usage: /sw:embed-acs <increment-id>
 ```
 
 ### Step 2: Validate Increment Structure
@@ -99,7 +99,7 @@ Usage: /specweave:embed-acs <increment-id>
    This increment may not have living docs, or they're in a different location.
 
    Please specify living docs path manually:
-     /specweave:embed-acs 0050 --living-docs-path <path>
+     /sw:embed-acs 0050 --living-docs-path <path>
    ```
 
 ### Step 4: Extract User Stories from spec.md
@@ -269,8 +269,8 @@ Usage: /specweave:embed-acs <increment-id>
 
    Next steps:
      1. Review embedded ACs in spec.md
-     2. Run: /specweave:validate 0050
-     3. Start work: /specweave:do
+     2. Run: /sw:validate 0050
+     3. Start work: /sw:do
    ```
 
 ## Flags (Optional)
@@ -280,7 +280,7 @@ Usage: /specweave:embed-acs <increment-id>
 Manually specify living docs path if auto-detection fails:
 
 ```bash
-/specweave:embed-acs 0050 --living-docs-path .specweave/docs/internal/specs/specweave/FS-048
+/sw:embed-acs 0050 --living-docs-path .specweave/docs/internal/specs/specweave/FS-048
 ```
 
 ### `--dry-run`
@@ -288,7 +288,7 @@ Manually specify living docs path if auto-detection fails:
 Preview what would be embedded without modifying files:
 
 ```bash
-/specweave:embed-acs 0050 --dry-run
+/sw:embed-acs 0050 --dry-run
 ```
 
 **Output**:
@@ -308,7 +308,7 @@ No files modified.
 Skip confirmation prompts:
 
 ```bash
-/specweave:embed-acs 0050 --force
+/sw:embed-acs 0050 --force
 ```
 
 ## Error Handling
@@ -323,7 +323,7 @@ Found: Directory does not exist
 Possible solutions:
   1. Check if feature_id in spec.md is correct
   2. Manually specify path: --living-docs-path <path>
-  3. Create living docs first: /specweave:sync-docs
+  3. Create living docs first: /sw:sync-docs
 ```
 
 ### No User Stories in spec.md
@@ -365,16 +365,16 @@ Skipping US-005 for now.
 
 This command is referenced by:
 
-1. **`/specweave:validate`**: Suggests running `/specweave:embed-acs` when ACs are missing
-2. **`/specweave:do`**: Pre-start hook suggests this command if validation fails
-3. **`/specweave:increment`**: Should auto-call this when creating `structure: user-stories` increments
+1. **`/sw:validate`**: Suggests running `/sw:embed-acs` when ACs are missing
+2. **`/sw:do`**: Pre-start hook suggests this command if validation fails
+3. **`/sw:increment`**: Should auto-call this when creating `structure: user-stories` increments
 
 ## Examples
 
 ### Example 1: Basic Usage
 
 ```bash
-/specweave:embed-acs 0050
+/sw:embed-acs 0050
 ```
 
 **Output**:
@@ -399,7 +399,7 @@ Extracting ACs...
 ### Example 2: Dry Run
 
 ```bash
-/specweave:embed-acs 0050 --dry-run
+/sw:embed-acs 0050 --dry-run
 ```
 
 **Output**:
@@ -415,7 +415,7 @@ To apply changes, run without --dry-run flag.
 ### Example 3: Manual Path
 
 ```bash
-/specweave:embed-acs 0050 --living-docs-path .specweave/docs/internal/specs/custom/FS-048
+/sw:embed-acs 0050 --living-docs-path .specweave/docs/internal/specs/custom/FS-048
 ```
 
 **Output**:
@@ -429,10 +429,10 @@ Extracting ACs...
 
 ## Related Commands
 
-- `/specweave:increment`: Create new increment (should auto-embed ACs)
-- `/specweave:validate`: Validate increment (checks AC presence)
-- `/specweave:do`: Start increment (pre-start hook validates ACs)
-- `/specweave:sync-docs`: Sync living documentation
+- `/sw:increment`: Create new increment (should auto-embed ACs)
+- `/sw:validate`: Validate increment (checks AC presence)
+- `/sw:do`: Start increment (pre-start hook validates ACs)
+- `/sw:sync-docs`: Sync living documentation
 
 ## Related Documentation
 

package/plugins/specweave/commands/{specweave-external.md → external.md}

@@ -1,12 +1,12 @@
 ---
-name: specweave:external
+name: sw:external
 description: View external items dashboard - open issues from GitHub, JIRA, and Azure DevOps
-usage: /specweave:external [--refresh]
+usage: /sw:external [--refresh]
 ---
 
 # External Items Dashboard
 
-**Usage**: `/specweave:external [--refresh]`
+**Usage**: `/sw:external [--refresh]`
 
 ---
 
@@ -53,7 +53,7 @@ Last updated: 2 minutes ago (use --refresh to update)
 Force refresh the cache and fetch latest data from all providers.
 
 ```bash
-/specweave:external --refresh
+/sw:external --refresh
 ```
 
 ---
@@ -130,21 +130,21 @@ Set environment variables:
 ## Integration Points
 
 External items are also shown in:
-- `/specweave:status` - Summary section at bottom
-- `/specweave:increment` - Notification after planning
-- `/specweave:progress` - Footer line
+- `/sw:status` - Summary section at bottom
+- `/sw:increment` - Notification after planning
+- `/sw:progress` - Footer line
 
 ---
 
 ## Related Commands
 
-- `/specweave:status` - Show increment status with external items summary
-- `/specweave:progress` - Show detailed progress with external items footer
-- `/specweave:import-external` - Import external items as increments
+- `/sw:status` - Show increment status with external items summary
+- `/sw:progress` - Show detailed progress with external items footer
+- `/sw:import-external` - Import external items as increments
 
 ---
 
-**Command**: `/specweave:external`
+**Command**: `/sw:external`
 **Plugin**: specweave (core)
 **Version**: v0.31.0+
 **Part of**: Increment 0109 - External Items Dashboard