specweave 0.33.5 → 0.34.0

package/plugins/specweave/commands/{specweave-check-tests.md → check-tests.md}

@@ -1,5 +1,5 @@
 ---
-name: specweave:check-tests
+name: sw:check-tests
 description: Validate test coverage for increment tasks, check AC-ID coverage, report test status, and verify coverage targets (NEW format with embedded tests in tasks.md)
 ---
 
@@ -22,16 +22,16 @@ Shows:
 
 ```bash
 # Check tests for current increment
-/specweave:check-tests
+/sw:check-tests
 
 # Check tests for specific increment
-/specweave:check-tests 0007
+/sw:check-tests 0007
 
 # Detailed report with test case breakdown
-/specweave:check-tests 0007 --detailed
+/sw:check-tests 0007 --detailed
 
 # AC-ID coverage report only
-/specweave:check-tests 0007 --ac-coverage
+/sw:check-tests 0007 --ac-coverage
 ```
 
 ---
@@ -58,7 +58,7 @@ Shows:
 ## Output Example (NEW Format)
 
 ```bash
-/specweave:check-tests 0007
+/sw:check-tests 0007
 
 📊 Test Status Report: 0007-smart-increment-discipline
 
@@ -138,7 +138,7 @@ Summary:
 ## Detailed Report (--detailed flag)
 
 ```bash
-/specweave:check-tests 0007 --detailed
+/sw:check-tests 0007 --detailed
 
 [Shows expanded report with:]
 - Full test case breakdown per task
@@ -153,7 +153,7 @@ Summary:
 ## AC Coverage Report (--ac-coverage flag)
 
 ```bash
-/specweave:check-tests 0007 --ac-coverage
+/sw:check-tests 0007 --ac-coverage
 
 ═══════════════════════════════════════════════════════════════
 
@@ -325,7 +325,7 @@ AC-US1-01 → Covered by T-001 ✅
 **If increment has tests.md** (pre-v0.7.0):
 
 ```bash
-/specweave:check-tests 0003  # Old format increment
+/sw:check-tests 0003  # Old format increment
 
 ⚠️  OLD FORMAT DETECTED: tests.md exists
 
@@ -365,12 +365,12 @@ if (hasTestsMd) {
    ```bash
    # Implement T-001
    # Write tests
-   /specweave:check-tests  # Verify tests pass
+   /sw:check-tests  # Verify tests pass
    ```
 
 2. **Before PR**: Ensure coverage meets targets
    ```bash
-   /specweave:check-tests 0007
+   /sw:check-tests 0007
    # Fix any failing tests
    # Commit and push
    ```
@@ -384,8 +384,8 @@ if (hasTestsMd) {
 
 4. **PM Gate 2**: Part of increment closure
    ```bash
-   /specweave:done 0007
-   # PM Agent runs /specweave:check-tests automatically
+   /sw:done 0007
+   # PM Agent runs /sw:check-tests automatically
    # Verifies >80% coverage before closure
    ```
 
@@ -396,7 +396,7 @@ if (hasTestsMd) {
 For CI/CD integration:
 
 ```bash
-/specweave:check-tests 0007
+/sw:check-tests 0007
 echo $?  # Exit code
 
 # Exit codes:

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

@@ -1,11 +1,11 @@
 ---
-name: specweave:costs
+name: sw:costs
 description: Display AI cost dashboard for current or specified increment with real-time savings tracking
 ---
 
 # Cost Dashboard Command
 
-You are being invoked via the `/specweave:costs [incrementId]` command.
+You are being invoked via the `/sw:costs [incrementId]` command.
 
 ## Your Task
 
@@ -206,7 +206,7 @@ COST BY INCREMENT
 
 ═══════════════════════════════════════════════════════════════
 
-💡 Tip: Use "/specweave:costs 0003" to see detailed report for increment 0003
+💡 Tip: Use "/sw:costs 0003" to see detailed report for increment 0003
 ```
 
 ## Error Handling
@@ -221,7 +221,7 @@ This could mean:
 - Cost tracking is not enabled
 - The cost log file is missing
 
-Run /specweave:do to start executing tasks with cost tracking enabled.
+Run /sw:do to start executing tasks with cost tracking enabled.
 ```
 
 ### Invalid Increment ID
@@ -234,7 +234,7 @@ Available increments:
 - 0002-core-enhancements
 - 0003-intelligent-model-selection
 
-Use /specweave:costs without arguments to see all increments.
+Use /sw:costs without arguments to see all increments.
 ```
 
 ## Important Notes
@@ -247,9 +247,9 @@ Use /specweave:costs without arguments to see all increments.
 
 ## Related Commands
 
-- `/specweave:do` - Execute tasks with cost tracking
-- `/specweave:progress` - View progress with cost summary
-- `/specweave:validate` - Validate increment (includes cost checks)
+- `/sw:do` - Execute tasks with cost tracking
+- `/sw:progress` - View progress with cost summary
+- `/sw:validate` - Validate increment (includes cost checks)
 
 ## Success Criteria
 

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

@@ -8,16 +8,16 @@ View and manage documentation discrepancies. Supports two modes:
 
 ```bash
 # Brownfield discrepancies (documentation gaps)
-/specweave:discrepancies                  # List pending brownfield discrepancies
-/specweave:discrepancies --module payment # Filter by module name
-/specweave:discrepancies --type missing-docs    # Filter by type
-/specweave:discrepancies --priority critical    # Filter by priority
-/specweave:discrepancies show DISC-0001   # View details
-/specweave:discrepancies ignore DISC-0001 "False positive"  # Ignore with reason
+/sw:discrepancies                  # List pending brownfield discrepancies
+/sw:discrepancies --module payment # Filter by module name
+/sw:discrepancies --type missing-docs    # Filter by type
+/sw:discrepancies --priority critical    # Filter by priority
+/sw:discrepancies show DISC-0001   # View details
+/sw:discrepancies ignore DISC-0001 "False positive"  # Ignore with reason
 
 # Code-to-spec discrepancies (legacy)
-/specweave:discrepancies --check          # Run code-spec check now
-/specweave:discrepancies --severity major # Filter by severity
+/sw:discrepancies --check          # Run code-spec check now
+/sw:discrepancies --severity major # Filter by severity
 ```
 
 ## Arguments
@@ -51,8 +51,8 @@ DISC-0003   ⚠️ MINOR      api-route          GET /api/orders path changed
 DISC-0004   ✅ TRIVIAL    type-definition    User type updated
 DISC-0005   ⚠️ MAJOR      api-route          New DELETE /api/users/:id
 
-Use '/specweave:discrepancies show <id>' to view details
-Use '/specweave:discrepancies accept <id>' to apply patch
+Use '/sw:discrepancies show <id>' to view details
+Use '/sw:discrepancies accept <id>' to apply patch
 ```
 
 ### show <id>
@@ -81,8 +81,8 @@ Description: Function signature has changed from documented version.
 Recommended: 👀 review-required
 Patch Available: Yes
 
-Use '/specweave:discrepancies accept DISC-0002' to apply patch
-Use '/specweave:discrepancies dismiss DISC-0002' to mark intentional
+Use '/sw:discrepancies accept DISC-0002' to apply patch
+Use '/sw:discrepancies dismiss DISC-0002' to mark intentional
 ```
 
 ### check
@@ -107,7 +107,7 @@ Results:
   - Minor: 1
   - Trivial: 1
 
-Use '/specweave:discrepancies' to view list
+Use '/sw:discrepancies' to view list
 ```
 
 ### accept <id>
@@ -137,5 +137,5 @@ Remaining: 4 discrepancies
 
 ## Related
 
-- `/specweave:sync-monitor`: Dashboard showing discrepancy count
-- `/specweave:notifications`: View discrepancy notifications
+- `/sw:sync-monitor`: Dashboard showing discrepancy count
+- `/sw:notifications`: View discrepancy notifications

package/plugins/specweave/commands/{specweave-discrepancy-to-increment.md → discrepancy-to-increment.md}

@@ -5,9 +5,9 @@ Convert one or more brownfield discrepancies into a new increment for systematic
 ## Usage
 
 ```bash
-/specweave:discrepancy-to-increment DISC-0001
-/specweave:discrepancy-to-increment DISC-0001 DISC-0002 DISC-0003
-/specweave:discrepancy-to-increment --module payment-service
+/sw:discrepancy-to-increment DISC-0001
+/sw:discrepancy-to-increment DISC-0001 DISC-0002 DISC-0003
+/sw:discrepancy-to-increment --module payment-service
 ```
 
 ## Arguments
@@ -40,7 +40,7 @@ Convert one or more brownfield discrepancies into a new increment for systematic
    - Add `incrementId` reference
 
 5. **On Increment Completion**
-   - When increment closes via `/specweave:done`
+   - When increment closes via `/sw:done`
    - All linked discrepancies auto-marked `resolved`
    - Archived to `resolved/YYYY-MM/`
 
@@ -71,8 +71,8 @@ Updated discrepancy status:
 
 Next steps:
   1. Review: .specweave/increments/0087-payment-docs-improvement/spec.md
-  2. Plan: /specweave:plan 0087
-  3. Execute: /specweave:do 0087
+  2. Plan: /sw:plan 0087
+  3. Execute: /sw:do 0087
 ```
 
 ## Generated Spec Structure
@@ -127,7 +127,7 @@ From DISC-0003:
 
 ## Completion Hook
 
-When the increment is closed with `/specweave:done`:
+When the increment is closed with `/sw:done`:
 
 ```typescript
 // Automatically triggered by increment completion
@@ -155,6 +155,6 @@ async function onIncrementComplete(incrementId: string) {
 
 ## Related
 
-- `/specweave:discrepancies` - View pending discrepancies
-- `/specweave:increment` - Create new increment manually
-- `/specweave:done` - Complete increment (triggers resolution)
+- `/sw:discrepancies` - View pending discrepancies
+- `/sw:increment` - Create new increment manually
+- `/sw:done` - Complete increment (triggers resolution)

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)