fix: revert stray specify.md changes + fix PowerShell -Number sentinel

- Reverted templates/commands/specify.md to upstream (unrelated edits
  from the cloud-edge workflow simplification had leaked into the PR)
- Changed PowerShell -Number default from 0 to -1 so that explicitly
  passing -Number 0 is correctly detected as explicit (fixes false
  negative where the guardrail wouldn't fire for prefix 000)

Author: daniel-graham

scripts/powershell/create-new-feature.ps1

@@ -4,7 +4,7 @@
 param(
     [switch]$Json,
     [string]$ShortName,
-    [int]$Number = 0,
+    [int]$Number = -1,
     [switch]$Help,
     [Parameter(ValueFromRemainingArguments = $true)]
     [string[]]$FeatureDescription
@@ -215,8 +215,8 @@ if ($ShortName) {
 # Determine branch number
 # Track whether the caller explicitly passed -Number so the guardrail below
 # only fires for explicit overrides, not for auto-detected numbers.
-$numberExplicit = ($Number -ne 0)
-if ($Number -eq 0) {
+$numberExplicit = ($Number -ge 0)
+if ($Number -lt 0) {
     if ($hasGit) {
         # Check existing branches on remotes
         $Number = Get-NextBranchNumber -SpecsDir $specsDir

templates/commands/specify.md

@@ -129,7 +129,7 @@ Given that feature description, do this:
 
    c. **Handle Validation Results**:
 
-      - **If all items pass**: Mark checklist complete and proceed to step 6
+      - **If all items pass**: Mark checklist complete and proceed to step 7
 
       - **If items fail (excluding [NEEDS CLARIFICATION])**:
         1. List the failing items and specific issues
@@ -178,8 +178,6 @@ Given that feature description, do this:
 
 **NOTE:** The script creates and checks out the new branch and initializes the spec file before writing.
 
-## General Guidelines
-
 ## Quick Guidelines
 
 - Focus on **WHAT** users need and **WHY**.