specweave 0.1.7 → 0.1.8

package/src/commands/inc.md

@@ -0,0 +1,85 @@
+---
+name: inc
+description: Shorthand for /increment - Plan new Product Increment (PM-led process)
+---
+
+# Plan Product Increment (Quick Alias)
+
+**⚡ Quick Alias**: This is a shorthand for `/increment`.
+
+This is the **most frequently used command** in SpecWeave's append-only increment workflow. Every new feature starts here.
+
+---
+
+## Why This Alias Exists
+
+In an append-only increment workflow:
+- `/increment` is your starting point for ALL new work
+- You'll use it dozens/hundreds of times
+- Short alias saves time and mental overhead
+- Other commands are used less frequently (no aliases needed)
+
+---
+
+## Usage
+
+```bash
+/inc "feature description"
+```
+
+**Examples**:
+```bash
+/inc "User authentication with JWT"
+/inc "Payment processing with Stripe"
+/inc "Real-time notifications"
+```
+
+---
+
+## What This Does
+
+Runs the full `/increment` command, which:
+
+1. **Detects tech stack** (TypeScript, Python, Go, etc.)
+2. **PM-led planning**:
+   - Market research
+   - Create spec.md (WHAT & WHY)
+   - Create plan.md (HOW)
+   - **Auto-generate tasks.md** from plan
+   - Create tests.md (test strategy)
+3. **Strategic agent review**:
+   - Architect designs system
+   - Security reviews threats
+   - QA defines test strategy
+   - DevOps plans infrastructure
+4. **User review checkpoint**
+5. **Ready to build**: `/build 0001`
+
+---
+
+## Typical Workflow
+
+```bash
+# 1. Plan increment (most common command - use alias!)
+/inc "User authentication"
+
+# 2. Review generated docs
+#    spec.md, plan.md, tasks.md, tests.md
+
+# 3. Build it
+/build 0001
+
+# 4. Validate quality (optional)
+/validate 0001 --quality
+
+# 5. Close when done
+/done 0001
+```
+
+---
+
+**💡 Pro Tip**: `/inc` is the ONLY aliased command. Use full names for others (`/build`, `/validate`, `/done`) to keep the workflow clear and explicit.
+
+---
+
+For complete documentation, see `/increment`.

package/src/commands/{validate-increment.md → validate.md}

@@ -1,5 +1,5 @@
 ---
-name: validate-increment
+name: validate
 description: Validate SpecWeave increment with rule-based checks and optional AI quality assessment
 ---
 

package/src/commands/add-tasks.md

@@ -1,176 +0,0 @@
-# /add-tasks - Add Tasks to Existing Increment
-
-**Command**: `/add-tasks <increment-id> <description> [options]`
-
-**Purpose**: Add new tasks to an existing increment during implementation
-
-**Framework**: Framework-agnostic (works with all tech stacks)
-
----
-
-## Usage
-
-```bash
-/add-tasks 001 "Fix error handling in context-loader"
-/add-tasks 001 --priority P2 "Add caching to skill-router"
-/add-tasks 001 "Multiple task lines..." --estimate "3 days"
-```
-
-## Arguments
-
-- `<increment-id>` (required): Increment number (e.g., `001`, `002`)
-- `<description>` (required): Task description
-- `--priority` (optional): P1/P2/P3 (default: P2)
-- `--estimate` (optional): Time estimate (default: detected from description)
-
----
-
-## When to Use
-
-**Add as task** ✅ when:
-- Duration: Hours-Days
-- Components affected: 1 agent/skill
-- Discovered during implementation
-- Examples: Bug fixes, small enhancements, error handling
-
-**Create new increment** ❌ when:
-- Duration: Weeks+
-- Components affected: 2+ agents/skills
-- Major new feature
-- Use `/create-increment` instead
-
----
-
-## Workflow
-
-### Step 1: Validate Increment
-
-```
-Validating increment 001-core-framework...
-
-→ Status: in-progress ✅ (can add tasks)
-→ Current tasks: 50
-→ Completed: 44 (88%)
-```
-
-**If increment not valid**:
-```
-❌ Cannot add tasks
-
-Reason: Increment 001 status is "closed"
-
-Options:
-A) Create new increment (recommended)
-B) Reopen 001 (if justified)
-```
-
-### Step 2: Auto-Increment Task ID
-
-```
-→ Scanning tasks.md for highest task ID...
-→ Found: T050
-→ New task ID: T051
-```
-
-### Step 3: Add to tasks.md
-
-```markdown
-## Additional Tasks (Added During Implementation)
-
-### T051: Fix error handling in context-loader
-**Added**: 2025-10-26
-**Discovered**: During integration testing
-**Priority**: P1
-**Estimated**: 2 hours
-**Status**: [ ] Pending
-
-**Implementation**:
-- Check if manifest file exists before parsing
-- Return helpful error message with file path
-- Log warning to .specweave/increments/0001-core-framework/logs/errors.log
-
-**Acceptance Criteria**:
-- [ ] Handles missing manifest gracefully
-- [ ] Error message includes file path
-- [ ] No crash when manifest not found
-```
-
-### Step 4: Update Frontmatter
-
-Update `spec.md`:
-
-```yaml
----
-updated: 2025-10-26      # ← Current date
-total_tasks: 51          # ← Incremented
-completed_tasks: 44      # ← Unchanged
-completion_rate: 86      # ← Recalculated (44/51)
----
-```
-
-### Step 5: Confirm
-
-```
-✅ Task added successfully
-
-Summary:
-→ Task ID: T051
-→ Description: Fix error handling in context-loader
-→ Priority: P1
-→ Increment: 001-core-framework
-→ Total tasks: 51 (was 50)
-→ Completion rate: 86% (was 88%)
-
-File: .specweave/increments/0001-core-framework/tasks.md
-```
-
----
-
-## Examples
-
-### Example 1: Bug Fix
-
-```bash
-/add-tasks 001 "Fix null pointer in skill-router when no skills installed"
-
-# Result:
-→ Task T052: Fix null pointer in skill-router
-→ Priority: P1 (critical bug)
-→ Estimated: 1 hour
-```
-
-### Example 2: Enhancement
-
-```bash
-/add-tasks 001 --priority P2 "Add caching to context-loader for better performance"
-
-# Result:
-→ Task T053: Add caching to context-loader
-→ Priority: P2 (enhancement)
-→ Estimated: 1 day
-```
-
-### Example 3: Multiple Tasks
-
-```bash
-/add-tasks 001 "Add error handling, logging, and validation to hetzner-provisioner"
-
-# Result:
-→ Task T054: Add error handling to hetzner-provisioner
-→ Task T055: Add logging to hetzner-provisioner
-→ Task T056: Add validation to hetzner-provisioner
-→ Priority: P2 (improvements)
-```
-
----
-
-## Related Documentation
-
-- [CLAUDE.md](../../CLAUDE.md#adding-tasks-to-current-increment) - Task addition guide
-- [INCREMENT-LIFECYCLE-DESIGN.md](../../.specweave/increments/0001-core-framework/reports/INCREMENT-LIFECYCLE-DESIGN.md) - Lifecycle design
-
----
-
-**Command Type**: Task management
-**Framework Support**: All
-**Impact**: Adds tasks to existing increment, updates completion rate

package/src/commands/at.md

@@ -1,114 +0,0 @@
----
-description: 🔥 Shorthand for /add-tasks - Add tasks to increment (Alias)
----
-
-# Add Tasks (Short Alias)
-
-**⚡ Quick Alias**: This is a shorthand command for `/add-tasks`.
-
-Use this when you want to quickly add tasks to an increment without typing the full command name.
-
----
-
-## Full Command
-
-For complete documentation, see `/add-tasks`.
-
-This alias provides the exact same functionality as the full command.
-
----
-
-## Usage
-
-```bash
-/at <increment-id> <task-description>
-```
-
-**Examples**:
-```bash
-/at 0001 "Implement login endpoint"
-/at 0001 "Add password validation"
-/at 0001 "Write E2E tests for auth flow"
-```
-
----
-
-## What This Does
-
-1. **Analyzes task** against spec/plan
-2. **Determines priority** (P1, P2, P3)
-3. **Estimates effort** (based on complexity)
-4. **Identifies dependencies** (from existing tasks)
-5. **Adds to tasks.md** with proper formatting
-6. **Updates progress** percentage
-
----
-
-## Task Format
-
-Tasks are added with:
-- ✅ **Task ID** (auto-numbered: T001, T002, ...)
-- ✅ **Description** (clear, actionable)
-- ✅ **Priority** (P1/P2/P3)
-- ✅ **Estimated time** (based on analysis)
-- ✅ **Dependencies** (if any)
-- ✅ **Status** (Pending by default)
-
-**Example Output**:
-```markdown
-### T012: Implement login endpoint
-**Priority**: P1
-**Estimated**: 2 hours
-**Depends on**: T008
-**Status**: [ ] Pending
-
-**Implementation**:
-- Create POST /api/auth/login endpoint
-- Validate email and password
-- Return JWT token on success
-- Handle rate limiting
-```
-
----
-
-## Bulk Add
-
-You can add multiple tasks by calling the command multiple times or providing a list:
-
-```bash
-/at 0001 "Task 1"
-/at 0001 "Task 2"
-/at 0001 "Task 3"
-```
-
----
-
-## When to Add Tasks
-
-**During planning**:
-- Breaking down large features
-- After spec/plan review
-
-**During implementation**:
-- Discovered new requirements
-- Technical debt identified
-- Bug fixes needed
-
-**After review**:
-- Feedback from code review
-- QA findings
-- Security audit results
-
----
-
-## Other Useful Aliases
-
-- `/ci` - Create increment (shorthand for `/create-increment`)
-- `/si` - Start increment (shorthand for `/start-increment`)
-- `/vi` - Validate increment (shorthand for `/validate-increment`)
-- `/done` - Close increment (shorthand for `/close-increment`)
-- `/ls` - List increments (shorthand for `/list-increments`)
-
----
-
-**💡 Tip**: Add tasks as you discover them - don't wait until sprint planning!