specweave 0.1.9 → 0.3.0

package/src/commands/specweave.next.md

@@ -0,0 +1,495 @@
+---
+name: specweave.next
+description: Smart increment transition - auto-close current if ready, intelligently suggest next work (backlog or new feature)
+---
+
+# Next Increment (Smart Workflow Transition)
+
+**Smart Workflow**: Seamlessly transition from current work to next, with automatic closure validation.
+
+You are helping the user complete their current increment and move to the next one with intelligent suggestions.
+
+## Usage
+
+```bash
+/next
+```
+
+**No arguments needed** - the command intelligently handles the transition.
+
+---
+
+## What This Does
+
+The `/next` command is your **workflow continuation** command. It:
+
+1. **Validates current increment** - Checks if work is complete
+2. **Auto-closes if ready** - PM validates and closes automatically
+3. **Suggests next work** - Intelligent recommendations from backlog or prompt for new
+4. **Smooth transition** - No manual `/done` + `/inc` needed
+
+---
+
+## Workflow
+
+### Step 1: Find Active Increment
+
+```bash
+# Check for in-progress increments
+find .specweave/increments -type f -name "spec.md" -exec grep -l "status: in-progress" {} \;
+```
+
+**Scenarios**:
+- ✅ One increment in-progress → Validate for closure
+- ⚠️ Multiple in-progress → Warn about WIP limit, ask which to close
+- ℹ️ None in-progress → Skip to Step 3 (suggest next work)
+
+### Step 2: PM Validation Gates (3 Gates)
+
+**🔥 CRITICAL: Run PM validation like `/done` command**
+
+Invoke PM validation for the in-progress increment:
+
+#### Gate 1: Tasks Completed ✅
+
+Check `tasks.md`:
+- [ ] All P1 (critical) tasks completed
+- [ ] All P2 (important) tasks completed OR deferred with reason
+- [ ] P3 (nice-to-have) tasks completed, deferred, or moved to backlog
+- [ ] No tasks in "blocked" state
+
+**Example check**:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+GATE 1: Tasks Completion
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Checking tasks.md for increment 0001...
+
+Priority P1 (Critical): 12 tasks
+  ✅ 12/12 completed (100%)
+
+Priority P2 (Important): 18 tasks
+  ✅ 16/18 completed (89%)
+  ⚠️ 2 deferred (documented reasons)
+
+Priority P3 (Nice-to-have): 12 tasks
+  ✅ 8/12 completed (67%)
+  📋 4 moved to backlog
+
+Status: ✅ PASS
+```
+
+#### Gate 2: Tests Passing ✅
+
+Run test suite:
+- [ ] All test suites passing (no failures)
+- [ ] Test coverage meets requirements (>80% for critical paths)
+- [ ] E2E tests passing (if UI exists)
+- [ ] No skipped tests without documentation
+
+**Example check**:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+GATE 2: Tests Passing
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Running test suite...
+
+Unit Tests: ✅ 47/47 passing (Coverage: 89%)
+Integration Tests: ✅ 15/15 passing
+E2E Tests: ✅ 8/8 passing
+
+Status: ✅ PASS
+```
+
+#### Gate 3: Documentation Updated ✅
+
+Check documentation:
+- [ ] CLAUDE.md updated with new features
+- [ ] README.md updated with usage examples
+- [ ] CHANGELOG.md updated (if public API changed)
+- [ ] API documentation regenerated (if applicable)
+
+**Example check**:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+GATE 3: Documentation Updated
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Checking documentation updates...
+
+CLAUDE.md: ✅ Updated with new features
+README.md: ✅ Examples added
+CHANGELOG.md: ✅ v0.1.7 entry created
+Inline Docs: ✅ All functions documented
+
+Status: ✅ PASS
+```
+
+### Step 3: Closure Decision
+
+**Based on PM validation results**:
+
+#### Scenario A: All Gates Pass ✅ (Auto-Close)
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+PM VALIDATION: ✅ READY TO CLOSE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+✅ Gate 1: Tasks (100% P1, 89% P2)
+✅ Gate 2: Tests (70/70 passing, 89% coverage)
+✅ Gate 3: Docs (all current)
+
+Increment 0001-user-authentication is complete!
+
+🎯 Auto-closing increment...
+  ✓ Updated status: in-progress → completed
+  ✓ Set completion date: 2025-10-28
+  ✓ Generated completion report
+  ✓ Freed WIP slot (1/2 → 0/2)
+
+🎉 Increment 0001 closed successfully!
+
+Proceeding to suggest next work...
+```
+
+#### Scenario B: One or More Gates Fail ❌ (Present Options)
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+PM VALIDATION: ❌ NOT READY TO CLOSE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+❌ Gate 1: Tasks - 2 P1 tasks incomplete
+✅ Gate 2: Tests - All passing
+❌ Gate 3: Docs - CLAUDE.md and README.md outdated
+
+Increment 0001-user-authentication is NOT ready to close.
+
+Options:
+A. Complete remaining work (recommended)
+   → Finish T005 (password hashing) - 2h
+   → Finish T008 (JWT validation) - 3h
+   → Update CLAUDE.md - 30m
+   → Update README.md - 1h
+   → Estimated: 6-7 hours
+
+B. Force close and defer incomplete tasks
+   → Move T005, T008 to next increment (0002)
+   → Close 0001 as "completed with deferrals"
+   → Document deferral reasons
+
+C. Stay on current increment
+   → Continue working on 0001
+   → Run `/specweave do 0001` to resume
+
+What would you like to do? [A/B/C]
+```
+
+**🔥 CRITICAL**: NEVER auto-close with incomplete work! Always give user control.
+
+### Step 4: Suggest Next Work (After Successful Closure)
+
+**Intelligent suggestions based on project state**:
+
+1. **Check for planned increments in backlog**:
+   ```bash
+   ls .specweave/increments/_backlog/*.md
+   # or
+   find .specweave/increments -name "spec.md" -exec grep -l "status: planned" {} \;
+   ```
+
+2. **Present options based on findings**:
+
+   **Option A: Backlog items found** ✅
+   ```
+   🎯 Next Work Suggestions
+
+   Found 2 planned increments in backlog:
+
+   1. 0002-payment-processing (P1)
+      → Stripe integration, payment flow
+      → Estimated: 2 weeks
+      → Dependencies: 0001 (✅ complete)
+
+   2. 0003-notification-system (P2)
+      → Email + SMS notifications
+      → Estimated: 1 week
+      → Dependencies: None
+
+   Recommendation: Start 0002-payment-processing (P1, ready to go)
+
+   Actions:
+   A. Start 0002 now → Run `/specweave do 0002`
+   B. Start 0003 instead → Run `/specweave do 0003`
+   C. Create new increment → Run `/specweave inc "feature name"`
+
+   What would you like to do? [A/B/C]
+   ```
+
+   **Option B: No backlog, but in-progress work exists** ⚠️
+   ```
+   🎯 Next Work Suggestions
+
+   Current WIP: 1/2 increments active
+   Active: 0002-payment-processing (50% complete)
+
+   Recommendation: Continue 0002-payment-processing
+
+   Next Action: Run `/specweave do 0002` to resume
+
+   💡 Tip: Run `/progress 0002` to see current status
+   ```
+
+   **Option C: Clean slate, no planned work** ✨
+   ```
+   🎯 Next Work Suggestions
+
+   No planned increments found.
+   Current WIP: 0/2 (both slots available)
+
+   Time to plan your next feature!
+
+   Options:
+   A. Create new increment → Run `/specweave inc "feature description"`
+      Example: /specweave inc "Admin dashboard"
+
+   B. Check existing ideas → Look in .specweave/increments/_backlog/
+      If you have ideas saved, promote them with /inc
+
+   C. Review roadmap → See .specweave/docs/internal/strategy/roadmap.md
+
+   💡 Tip: Start with the most valuable feature for users!
+   ```
+
+---
+
+## Example Workflows
+
+### Example 1: Happy Path (Auto-Close and Continue)
+
+**User**:
+```bash
+/next
+```
+
+**Output**:
+```
+📊 Checking current increment...
+
+Active: 0001-user-authentication
+
+🔍 PM Validation:
+  ✅ Gate 1: All P1 tasks complete (12/12)
+  ✅ Gate 2: All tests passing (70/70, 89% coverage)
+  ✅ Gate 3: Documentation updated
+
+🎯 Auto-closing increment 0001...
+  ✓ Status: completed
+  ✓ Completion report generated
+  ✓ WIP freed (1/2 → 0/2)
+
+🎉 Increment 0001 closed successfully!
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+🎯 Next Work Suggestions
+
+Found 1 planned increment:
+
+0002-payment-processing (P1)
+  → Stripe integration, payment flow
+  → Estimated: 2 weeks
+  → Dependencies: 0001 (✅ complete)
+
+Recommendation: Start 0002-payment-processing
+
+Next Action: Run `/specweave do 0002` to begin
+
+💡 Tip: Review spec first with `cat .specweave/increments/0002-payment-processing/spec.md`
+```
+
+### Example 2: Incomplete Work (User Decision)
+
+**User**:
+```bash
+/next
+```
+
+**Output**:
+```
+📊 Checking current increment...
+
+Active: 0001-user-authentication
+
+🔍 PM Validation:
+  ❌ Gate 1: 2 P1 tasks incomplete (10/12)
+  ✅ Gate 2: All tests passing
+  ❌ Gate 3: README.md not updated
+
+Increment 0001 is NOT ready to close.
+
+Blockers:
+  • T010: Add rate limiting (P1) - 2 hours
+  • T012: Add password reset (P1) - 3 hours
+  • README.md update - 1 hour
+
+Options:
+A. Complete remaining work (recommended) → 6 hours
+B. Force close and defer T010, T012 to 0002
+C. Stay on 0001 and continue working
+
+What would you like to do? [A/B/C] _
+```
+
+**User types "A"**:
+```
+✅ Good choice! Let's finish 0001 properly.
+
+Next Action: Run `/specweave do 0001` to resume at T010
+
+💡 Tip: `/specweave progress` shows your current status anytime
+```
+
+### Example 3: No Active Work (Clean Start)
+
+**User**:
+```bash
+/next
+```
+
+**Output**:
+```
+📊 Checking current increment...
+
+No active increments found.
+
+Recent work:
+  ✅ 0001-user-authentication (closed 2 days ago)
+  ✅ 0002-payment-processing (closed 1 week ago)
+
+Current WIP: 0/2 (both slots available)
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+🎯 Next Work Suggestions
+
+No planned increments found. Time to plan new work!
+
+Options:
+1. Create new increment:
+   → Run `/specweave inc "feature description"`
+   → Example: /specweave inc "Admin dashboard"
+
+2. Check backlog for ideas:
+   → Look in .specweave/increments/_backlog/
+   → Promote with `/specweave inc "feature name"`
+
+3. Review roadmap:
+   → See .specweave/docs/internal/strategy/roadmap.md
+
+💡 Tip: Focus on the most valuable feature for users!
+```
+
+### Example 4: Multiple In-Progress (WIP Limit Warning)
+
+**User**:
+```bash
+/next
+```
+
+**Output**:
+```
+📊 Checking current increment...
+
+⚠️ Warning: Multiple increments in-progress (2/2 at WIP limit)
+
+Active increments:
+1. 0002-payment-processing (50% complete)
+   → Last activity: 2 hours ago
+   → Next task: T008
+
+2. 0003-notification-system (25% complete)
+   → Last activity: 1 day ago
+   → Next task: T004
+
+Recommendation: Focus on completing one before starting new work.
+
+Which increment should we focus on closing?
+A. Close 0002-payment-processing
+B. Close 0003-notification-system
+C. Cancel (continue working as-is)
+
+Your choice? [A/B/C] _
+```
+
+---
+
+## Key Differences from Other Commands
+
+| Command | Purpose | When to Use |
+|---------|---------|-------------|
+| `/specweave inc "feature"` | Create NEW increment with specific feature | Starting fresh work |
+| `/specweave do` | Execute tasks in increment | Implementing planned work |
+| `/specweave progress` | Check status (no action) | Quick status check |
+| `/done` | Explicitly close increment | Manual closure with validation |
+| `/next` ⭐ | **Smart transition** (close + suggest next) | **Natural workflow continuation** |
+
+**Why `/next` is special**:
+- ✅ Combines validation + closure + suggestion in one command
+- ✅ No need to remember `/done` then `/inc` or `/specweave do`
+- ✅ Intelligent suggestions (backlog, WIP, new work)
+- ✅ User stays in control (never forces actions)
+- ✅ Natural "what's next?" workflow
+
+---
+
+## Best Practices
+
+1. **Run `/next` when you feel done** - It validates completion and suggests next steps
+2. **Trust the PM validation** - If gates fail, there's unfinished work
+3. **Follow recommendations** - Backlog items are already planned
+4. **Keep WIP limit in mind** - Don't force multiple increments
+5. **Use `/specweave progress` for status** - `/next` is for transitions
+
+---
+
+## Related Commands
+
+- `/inc` - Create new increment (PM-led planning)
+- `/specweave do` - Execute tasks (auto-resumes)
+- `/specweave progress` - Check status
+- `/done` - Manual closure with PM validation
+- `/list-increments` - View all increments
+
+---
+
+## Configuration
+
+**File**: `.specweave/config.yaml`
+
+```yaml
+workflow:
+  auto_close:
+    enabled: true              # Enable auto-close in /next
+    strict_mode: true          # Require all 3 gates to pass
+    suggest_next: true         # Suggest next work after closure
+
+  pm_validation:
+    gates:
+      tasks:
+        require_p1_complete: true
+        require_p2_complete: false  # P2 can be deferred
+      tests:
+        require_all_passing: true
+        min_coverage: 80
+      documentation:
+        require_claude_md: true
+        require_readme: true
+```
+
+---
+
+**💡 Remember**: `/next` is your **"I'm done, what's next?"** command. It handles the transition intelligently so you can stay in flow!

package/src/commands/{progress.md → specweave.progress.md}

@@ -1,5 +1,5 @@
 ---
-name: progress
+name: specweave.progress
 description: Show current increment progress, task completion %, PM gate status, and next action
 ---
 
@@ -78,9 +78,9 @@ PM Gates Preview:
 └─ Gate 3 (Docs): CLAUDE.md ✅, README.md ⏳
 
 Last Activity: 5 minutes ago
-Next Action: Run `/build 0001` to resume at T004
+Next Action: Run `/do 0001` to resume at T004
 
-💡 Tip: `/build` auto-resumes from last incomplete task!
+💡 Tip: `/do` auto-resumes from last incomplete task!
 ```
 
 ### No Active Work
@@ -95,7 +95,7 @@ Recent Increments:
 ├─ 0002-user-profile (completed) - 2 days ago
 └─ 0001-auth (closed) - 3 days ago
 
-Next Action: Run `/inc "feature description"` to start new work
+Next Action: Run `/specweave inc "feature description"` to start new work
 
 💡 Tip: `/inc` is your starting point for all new features
 ```
@@ -116,7 +116,7 @@ Active Increments:
 
 Recommendation: Focus on completing 0002 before starting new work.
 
-Next Action: Run `/build 0002` to continue payment-flow
+Next Action: Run `/do 0002` to continue payment-flow
 ```
 
 ### Stuck/Inactive Increment
@@ -140,7 +140,7 @@ Task Progress: 4/12 completed (33%)
 └─ 6 more tasks...
 
 Next Action:
-1. Run `/build 0001` to retry T005
+1. Run `/do 0001` to retry T005
 2. Or manually review T005 for blockers
 3. Or skip T005 and defer to next increment
 
@@ -201,9 +201,9 @@ if [[ $in_progress_count -eq 0 ]]; then
     echo "Run \`/inc\` to start new feature"
 elif [[ $in_progress_count -gt 1 ]]; then
     echo "⚠️ Multiple increments active. Focus on completing one."
-    echo "Run \`/build $oldest_increment\`"
+    echo "Run \`/do $oldest_increment\`"
 elif [[ $next_task != "" ]]; then
-    echo "Run \`/build $increment_id\` to resume at $next_task"
+    echo "Run \`/do $increment_id\` to resume at $next_task"
 else
     echo "All tasks complete! Run \`/done $increment_id\` to close."
 fi
@@ -228,9 +228,9 @@ Use `/progress` when you:
 /progress
 
 # Shows: "Active: 0002-payments, Task 5/10 (50%)"
-# Shows: "Next: /build 0002 to resume at T006"
+# Shows: "Next: /do 0002 to resume at T006"
 
-/build 0002
+/do 0002
 # Auto-resumes from T006
 ```
 
@@ -239,7 +239,7 @@ Use `/progress` when you:
 ## Pro Tips
 
 1. **No increment ID needed** - `/progress` automatically finds active increment
-2. **Smart resume** - `/build` picks up where you left off (no task ID needed)
+2. **Smart resume** - `/do` picks up where you left off (no task ID needed)
 3. **WIP limits** - Keep 1-2 increments active max for focus
 4. **Completion %** - P1 tasks weighted higher (they're critical path)
 5. **Time tracking** - Warns if tasks are stuck (>2 hours inactive)
@@ -249,7 +249,7 @@ Use `/progress` when you:
 ## Related Commands
 
 - `/inc` - Start new increment (auto-closes previous if ready)
-- `/build` - Execute tasks (auto-resumes from next incomplete)
+- `/do` - Execute tasks (auto-resumes from next incomplete)
 - `/validate` - Run quality checks (optional)
 - `/done` - Explicitly close increment (optional if `/inc` auto-closes)