specweave 0.4.1 → 0.6.0

package/{src → plugins/specweave-core}/commands/specweave.increment.md

@@ -11,9 +11,82 @@ You are helping the user create a new SpecWeave increment with automatic closure
 
 ## Steps:
 
-### Step 0: Smart Check Previous Increment (if applicable)
+### Step 0A: STRICT Pre-Flight Check (MANDATORY - v0.6.0+)
 
-**🎯 CRITICAL: Suggest, don't force** - help user make informed decision!
+**⛔ THE IRON RULE: Cannot start increment N+1 until increment N is DONE**
+
+**THIS IS NOT NEGOTIABLE** - Enforce strict increment discipline!
+
+```typescript
+// Import increment status detector
+import { IncrementStatusDetector } from '../core/increment-status';
+
+// Check for incomplete increments
+const detector = new IncrementStatusDetector();
+const incomplete = await detector.getAllIncomplete();
+
+if (incomplete.length > 0) {
+  // ❌ BLOCK IMMEDIATELY - Show error and exit
+  console.log(chalk.red.bold('\n❌ Cannot create new increment!\n'));
+
+  console.log(chalk.yellow('Previous increments are incomplete:\n'));
+
+  incomplete.forEach(status => {
+    console.log(chalk.yellow(`📋 Increment ${status.id}`));
+    console.log(`   Status: ${status.percentComplete}% complete (${status.completedTasks}/${status.totalTasks} tasks)`);
+
+    if (status.pendingTasks.length <= 5) {
+      console.log('   Pending:');
+      status.pendingTasks.forEach(task => {
+        console.log(`     - ${task.id}: ${task.title}`);
+      });
+    } else {
+      console.log(`   Pending: ${status.pendingTasks.length} tasks`);
+    }
+    console.log('');
+  });
+
+  console.log(chalk.blue('💡 What would you like to do?\n'));
+  console.log(chalk.white('1️⃣  Close incomplete increments:'));
+  console.log(chalk.dim('   /specweave:close\n'));
+
+  console.log(chalk.white('2️⃣  Check status:'));
+  console.log(chalk.dim('   /specweave:status\n'));
+
+  console.log(chalk.white('3️⃣  Force create (DANGEROUS - violates discipline!):'));
+  console.log(chalk.dim('   Add --force flag to bypass this check\n'));
+
+  console.log(chalk.yellow.bold('⚠️  The discipline exists for a reason:'));
+  console.log(chalk.yellow('   - Prevents scope creep'));
+  console.log(chalk.yellow('   - Ensures completions are tracked'));
+  console.log(chalk.yellow('   - Maintains living docs accuracy'));
+  console.log(chalk.yellow('   - Keeps work focused\n'));
+
+  // Exit - do NOT proceed
+  process.exit(1);
+}
+```
+
+**Why This is Strict** (changed from v0.5.0):
+- ❌ NO "suggest, don't force" - this IS forced
+- ❌ NO options to defer - close previous first
+- ❌ NO auto-closing gates - explicit closure required
+- ✅ HARD BLOCK - cannot proceed without closing previous
+- ✅ Clear next steps - use `/specweave:close`
+- ✅ Safety valve - `--force` flag for emergencies (logged)
+
+**Rationale**:
+- Increments pile up without discipline (see: 0002, 0003, 0006 all incomplete)
+- "Suggest" approach failed - users ignore suggestions
+- Living docs become stale when increments stay open
+- Multiple incomplete increments = no source of truth
+- Force discipline = force quality
+
+### Step 0B: Smart Check Previous Increment (if applicable)
+
+**🎯 ONLY RUNS IF Step 0A passes** (no incomplete increments)
+
+This step handles auto-closing the previous increment if it's ready.
 
 1. **Check for in-progress increments**:
    ```bash
@@ -26,24 +99,16 @@ You are helping the user create a new SpecWeave increment with automatic closure
    - **Gate 2**: Tests passing (>80% coverage)?
    - **Gate 3**: Documentation updated (CLAUDE.md, README.md)?
 
-3. **Decision matrix** (NEVER force, ALWAYS suggest):
+3. **Decision matrix**:
    ```
    All gates ✅ → Auto-close previous, create new (seamless)
 
-   Any gate ❌ → STOP and present options (user decides):
-      Option A: Complete 0001 first (recommended)
-         → Finish remaining work before starting new
-
-      Option B: Move incomplete tasks to 0002
-         → Transfer T006, T007 to new increment
-         → Close 0001 as "completed with deferrals"
-
-      Option C: Cancel new increment
-         → Stay on 0001, continue working
-         → User will retry /inc when ready
+   Any gate ❌ → This should never happen (caught by Step 0A)
+                 → If it does, treat as incomplete and block
    ```
 
-**CRITICAL**: NEVER auto-close with incomplete work! Always give user control.
+**NOTE**: Step 0B is now mostly redundant - Step 0A already blocks incomplete work.
+This step remains for auto-closing "in-progress" increments that ARE complete.
 
 4. **Auto-close output** (if gates pass):
    ```
@@ -297,10 +362,10 @@ After the increment-planner skill completes, verify:
 📝 Now syncing strategic documentation to living docs...
 ```
 
-**Run `/sync-docs update` to create initial documentation**:
+**Run `/specweave:sync-docs update` to create initial documentation**:
 
 ```bash
-/sync-docs update
+/specweave:sync-docs update
 ```
 
 This will:
@@ -311,7 +376,7 @@ This will:
 - Update security docs in `.specweave/docs/internal/security/`
 - May prompt for conflict resolution if needed
 
-**After `/sync-docs update` completes**:
+**After `/specweave:sync-docs update` completes**:
 
 ```
 ✅ Strategic documentation synchronized!

package/{src → plugins/specweave-core}/commands/specweave.md

@@ -39,6 +39,16 @@ This master command routes to SpecWeave increment lifecycle subcommands.
 | **sync-github** | Sync increment to GitHub issues | `/specweave sync-github 0001` |
 | **sync-jira** | Sync increment to Jira epics/stories | `/specweave sync-jira import SCRUM-123` |
 
+### GitHub Plugin
+
+| Subcommand | Description | Example |
+|------------|-------------|---------|
+| **github.create-issue** | Create GitHub issue from increment | `/specweave github.create-issue 0001` |
+| **github.sync** | Bidirectional sync with GitHub | `/specweave github.sync 0001` |
+| **github.sync-tasks** | Sync tasks as GitHub sub-issues | `/specweave github.sync-tasks 0001` |
+| **github.close-issue** | Close GitHub issue | `/specweave github.close-issue 0001` |
+| **github.status** | Show GitHub sync status | `/specweave github.status` |
+
 ---
 
 ## Subcommand Routing
@@ -53,14 +63,21 @@ This master command routes to SpecWeave increment lifecycle subcommands.
 
 ```yaml
 subcommands:
-  inc: .claude/commands/specweave.inc.md
-  build: .claude/commands/specweave.do.md
-  next: .claude/commands/specweave.next.md
-  done: .claude/commands/specweave.done.md
-  progress: .claude/commands/specweave.progress.md
-  validate: .claude/commands/specweave.validate.md
-  sync-github: .claude/commands/specweave.sync-github.md
-  sync-jira: .claude/commands/specweave.sync-jira.md
+  inc: .claude/commands/specweave:inc.md
+  build: .claude/commands/specweave:do.md
+  next: .claude/commands/specweave:next.md
+  done: .claude/commands/specweave:done.md
+  progress: .claude/commands/specweave:progress.md
+  validate: .claude/commands/specweave:validate.md
+  sync-github: .claude/commands/specweave:sync-github.md
+  sync-jira: .claude/commands/specweave:sync-jira.md
+
+  # GitHub Plugin Commands
+  github.create-issue: .claude/commands/specweave.github.github-create-issue.md
+  github.sync: .claude/commands/specweave.github.github-sync.md
+  github.sync-tasks: .claude/commands/specweave.github.github-sync-tasks.md
+  github.close-issue: .claude/commands/specweave.github.github-close-issue.md
+  github.status: .claude/commands/specweave.github.github-status.md
 ```
 
 ---
@@ -90,7 +107,7 @@ Else:
 ### Step 3: Route to Command
 
 ```
-Read file: .claude/commands/specweave.inc.md
+Read file: .claude/commands/specweave:inc.md
 Execute: Command content with arguments
 ```
 
@@ -108,8 +125,8 @@ Execute: Command content with arguments
 **Routing**:
 ```
 Parse: subcommand = "inc", args = ["User authentication"]
-Route to: .claude/commands/specweave.inc.md
-Execute: /specweave.inc "User authentication"
+Route to: .claude/commands/specweave:inc.md
+Execute: /specweave:inc "User authentication"
 ```
 
 ### Example 2: Build Current Increment
@@ -122,8 +139,8 @@ Execute: /specweave.inc "User authentication"
 **Routing**:
 ```
 Parse: subcommand = "build", args = []
-Route to: .claude/commands/specweave.do.md
-Execute: /specweave.do (auto-finds active increment)
+Route to: .claude/commands/specweave:do.md
+Execute: /specweave:do (auto-finds active increment)
 ```
 
 ### Example 3: Smart Transition
@@ -136,8 +153,8 @@ Execute: /specweave.do (auto-finds active increment)
 **Routing**:
 ```
 Parse: subcommand = "next", args = []
-Route to: .claude/commands/specweave.next.md
-Execute: /specweave.next (validates, closes, suggests)
+Route to: .claude/commands/specweave:next.md
+Execute: /specweave:next (validates, closes, suggests)
 ```
 
 ### Example 4: Invalid Subcommand
@@ -165,8 +182,16 @@ Available subcommands:
     sync-github     - Sync to GitHub
     sync-docs       - Sync documentation (review/update)
 
+  GitHub Plugin:
+    github.create-issue  - Create GitHub issue from increment
+    github.sync          - Bidirectional sync with GitHub
+    github.sync-tasks    - Sync tasks as GitHub sub-issues
+    github.close-issue   - Close GitHub issue
+    github.status        - Show GitHub sync status
+
 Usage: /specweave <subcommand> [arguments]
 Example: /specweave inc "User authentication"
+Example: /specweave github.create-issue 0001
 ```
 
 ---
@@ -228,7 +253,7 @@ User's project:
   .claude/commands/do.md    (their own build command)
 
 SpecWeave installation:
-  .claude/commands/specweave.do.md    (SpecWeave's build)
+  .claude/commands/specweave:do.md    (SpecWeave's build)
   .claude/commands/specweave.md          (master router)
 
 Result: ✅ NO COLLISION - Both coexist!
@@ -353,7 +378,7 @@ If you have code/docs referencing old commands:
 /progress         → /specweave progress
 /validate         → /specweave validate
 /sync-github      → /specweave sync-github
-/sync-docs        → /specweave sync-docs
+/specweave:sync-docs        → /specweave sync-docs
 ```
 
 ### Automated Migration Script
@@ -407,6 +432,13 @@ Project Setup:
   sync-github <id>   - Sync increment to GitHub issues
   sync-docs [mode] [id] - Sync documentation (review/update)
 
+GitHub Plugin:
+  github.create-issue <id>  - Create GitHub issue from increment
+  github.sync <id>          - Bidirectional sync with GitHub
+  github.sync-tasks <id>    - Sync tasks as GitHub sub-issues
+  github.close-issue <id>   - Close GitHub issue
+  github.status             - Show GitHub sync status
+
 Examples:
   /specweave inc "User authentication"
   /specweave do

package/{src → plugins/specweave-core}/commands/specweave.sync-docs.md

@@ -581,7 +581,7 @@ Documentation is now in sync with increment {increment_id}! 🎉
 Available increments:
   {list .specweave/increments/*/}
 
-Usage: /sync-docs [review|update] [increment_id]
+Usage: /specweave:sync-docs [review|update] [increment_id]
 ```
 
 ### Error: No Increment Files
@@ -605,7 +605,7 @@ Valid modes:
   - update (post-implementation doc sync)
   - [none] (auto-detect based on status)
 
-Usage: /sync-docs [review|update] [increment_id]
+Usage: /specweave:sync-docs [review|update] [increment_id]
 ```
 
 ---
@@ -614,7 +614,7 @@ Usage: /sync-docs [review|update] [increment_id]
 
 ### Example 1: Auto-detect mode for current increment
 ```
-User: /sync-docs
+User: /specweave:sync-docs
 
 Output:
 🔍 Detected increment: 0002
@@ -627,7 +627,7 @@ Proceeding with UPDATE mode...
 
 ### Example 2: Explicit review mode
 ```
-User: /sync-docs review 0003
+User: /specweave:sync-docs review 0003
 
 Output:
 🔍 Increment: 0003
@@ -639,7 +639,7 @@ Output:
 
 ### Example 3: Explicit update mode with increment
 ```
-User: /sync-docs update 0002
+User: /specweave:sync-docs update 0002
 
 Output:
 🔍 Increment: 0002