specweave 0.1.7 → 0.1.8

package/src/commands/start-increment.md

@@ -1,139 +0,0 @@
-# /start-increment - Start Planned Increment
-
-**Command**: `/start-increment <increment-id> [options]`
-
-**Purpose**: Change increment status from "planned" to "in-progress" (with WIP limit check)
-
-**Framework**: Framework-agnostic (works with all tech stacks)
-
----
-
-## Usage
-
-```bash
-/start-increment 002                 # Start increment 002
-/start-increment 002 --force         # Override WIP limit (use sparingly)
-```
-
-## Arguments
-
-- `<increment-id>` (required): Increment number (e.g., `001`, `002`)
-- `--force` (optional): Override WIP limit check
-
----
-
-## Workflow
-
-### Step 1: Check WIP Limit
-
-```
-Checking WIP limit...
-
-→ Current WIP: 2/2 (at limit)
-→ Increments in progress:
-  - 001-core-framework (88% complete)
-  - 003-jira-integration (40% complete)
-
-⚠️ WIP limit reached (2/2)
-
-Cannot start 002 without closing an existing increment.
-
-Options:
-A) Close 001-core-framework (88% done, ready to close)
-   Run: /close-increment 001
-
-B) Close 003-jira-integration (40% done, transfer leftovers)
-   Run: /close-increment 003
-
-C) Wait until 001 or 003 completes
-
-D) Override WIP limit (not recommended)
-   Run: /start-increment 002 --force
-
-Your choice?
-```
-
-### Step 2: Check Dependencies
-
-```
-Checking dependencies...
-
-→ Increment 002 depends on: 001-core-framework
-→ Dependency status: in-progress (88% complete)
-
-⚠️ Dependency 001 not yet completed
-
-Options:
-A) Wait for 001 to complete (recommended)
-B) Start anyway if 001 is far enough along
-   (If 002 only needs partial 001 functionality)
-
-Your choice?
-```
-
-### Step 3: Start Increment
-
-**If checks pass**:
-
-```
-✅ Starting increment 002-enhancements...
-
-→ Status: planned → in-progress
-→ Started: 2025-10-26
-→ WIP: 1/2 (slot 1 assigned)
-→ Creating execution log...
-```
-
-Update `spec.md` frontmatter:
-
-```yaml
----
-status: in-progress      # ← Changed from "planned"
-started: 2025-10-26      # ← Start date
-wip_slot: 1              # ← WIP slot assigned
----
-```
-
-Create initial log entry:
-
-```markdown
-# Execution Log
-
-## 2025-10-26: Increment Started
-- Status: planned → in-progress
-- Total tasks: 15
-- Dependencies: 001-core-framework (completed)
-- Estimated duration: 2 weeks
-```
-
-### Step 4: Confirm
-
-```
-✅ Increment 002-enhancements started
-
-Summary:
-→ Status: in-progress
-→ Started: 2025-10-26
-→ Total tasks: 15
-→ WIP: 1/2
-→ Estimated completion: 2025-11-09 (2 weeks)
-
-Next steps:
-1. Review tasks.md
-2. Start with first P1 task
-3. Mark tasks complete as you go
-4. Close with /close-increment 002 when P1 tasks done
-```
-
----
-
-## Related Documentation
-
-- [CLAUDE.md](../../CLAUDE.md#increment-lifecycle-management) - Lifecycle guide
-- [INCREMENT-LIFECYCLE-DESIGN.md](../../.specweave/increments/0001-core-framework/reports/INCREMENT-LIFECYCLE-DESIGN.md) - Lifecycle design
-
----
-
-**Command Type**: Lifecycle management
-**Framework Support**: All
-**WIP Impact**: Occupies 1 WIP slot

package/src/commands/vi.md

@@ -1,89 +0,0 @@
----
-description: 🔥 Shorthand for /validate-increment - Validate increment quality (Alias)
----
-
-# Validate Increment (Short Alias)
-
-**⚡ Quick Alias**: This is a shorthand command for `/validate-increment`.
-
-Use this when you want to quickly validate an increment without typing the full command name.
-
----
-
-## Full Command
-
-For complete documentation, see `/validate-increment`.
-
-This alias provides the exact same functionality as the full command.
-
----
-
-## Usage
-
-```bash
-/vi [increment-id] [--quality]
-```
-
-**Examples**:
-```bash
-/vi 0001                    # Rule-based validation only
-/vi 0001 --quality          # Rule-based + LLM quality assessment
-/vi                         # Validate current increment
-```
-
----
-
-## What This Does
-
-**Rule-Based Validation** (Always runs):
-- ✅ 120 validation rules across 4 categories
-- ✅ Consistency checks (Spec ↔ Plan ↔ Tasks alignment)
-- ✅ Completeness checks (All required sections present)
-- ✅ Quality checks (Technology-agnostic, testable criteria)
-- ✅ Traceability checks (TC-0001 → tests.md coverage)
-
-**LLM Quality Assessment** (With `--quality` flag):
-- ✅ 6-dimension scoring (Clarity, Testability, Completeness, etc.)
-- ✅ Actionable suggestions with examples
-- ✅ Overall quality score (0-100)
-- ✅ Issue severity ranking (major, minor)
-
----
-
-## Validation Results
-
-**Rule-Based Output**:
-```
-✅ Validation Results: 118/120 rules passed (98%)
-
-Issues Found:
-⚠️ [CONSISTENCY-012] Missing test case coverage for US-B003
-⚠️ [QUALITY-008] Acceptance criteria not testable in spec.md:45
-```
-
-**Quality Assessment Output** (with `--quality`):
-```
-🔍 Quality Score: 87/100 (GOOD)
-
-Dimension Scores:
-  • Clarity:         92/100 ✓✓
-  • Testability:     78/100 ✓  (Needs improvement)
-  • Completeness:    90/100 ✓✓
-  • Feasibility:     88/100 ✓✓
-
-Issues: 2 major, 1 minor
-Suggestions: 3 high priority improvements
-```
-
----
-
-## Other Useful Aliases
-
-- `/ci` - Create increment (shorthand for `/create-increment`)
-- `/si` - Start increment (shorthand for `/start-increment`)
-- `/done` - Close increment (shorthand for `/close-increment`)
-- `/ls` - List increments (shorthand for `/list-increments`)
-
----
-
-**💡 Tip**: Use `/vi` for quick checks, `/vi --quality` before implementation.