specweave 0.28.22 → 0.28.25

package/plugins/specweave-ado/commands/specweave-ado-sync.md

@@ -1,29 +1,29 @@
 ---
 name: specweave-ado:sync
-description: Bidirectional sync between SpecWeave increment and Azure DevOps work item (two-way sync by default)
+description: Two-way sync between SpecWeave increment and Azure DevOps work item (push & pull by default)
 ---
 
 # Sync ADO Work Item Command
 
 **Usage**: `/specweave-ado:sync <increment-id> [options]`
 
-**Purpose**: Bidirectional synchronization between SpecWeave increment and Azure DevOps work item
+**Purpose**: Two-way synchronization between SpecWeave increment and Azure DevOps work item
 
-**Default**: Two-way sync (bidirectional)
+**Default**: Two-way sync (push & pull)
 
 ---
 
 ## Options
 
-- `--direction <mode>`: Sync direction (default: `bidirectional`)
-  - `bidirectional`: SpecWeave ↔ ADO (default - recommended)
+- `--direction <mode>`: Sync direction (default: `two-way`)
+  - `two-way`: SpecWeave ↔ ADO (default - recommended)
   - `to-ado`: SpecWeave → ADO only (push progress)
   - `from-ado`: ADO → SpecWeave only (pull updates)
 
 ## Examples
 
 ```bash
-# Bidirectional sync (default - two-way)
+# Two-way sync (default - both directions)
 /specweave-ado:sync 0005
 
 # Push only (one-way to ADO)
@@ -37,7 +37,7 @@ description: Bidirectional sync between SpecWeave increment and Azure DevOps wor
 
 ## Command Behavior
 
-When user runs this command, invoke `ado-manager` agent to perform bidirectional sync:
+When user runs this command, invoke `ado-manager` agent to perform two-way sync:
 
 ### Phase 1: Pull FROM ADO (default behavior)
 1. Fetch work item state from ADO API
@@ -66,7 +66,7 @@ When user runs this command, invoke `ado-manager` agent to perform bidirectional
 ```
 Use Task tool with subagent_type: "specweave-ado:ado-manager:ado-manager"
 
-Prompt: "Bidirectional sync for increment 0005-payment-integration with ADO.
+Prompt: "Two-way sync for increment 0005-payment-integration with ADO.
 
 Phase 1 - Pull FROM ADO:
 1. Fetch work item #12345 from ADO API
@@ -83,20 +83,20 @@ Phase 2 - Push TO ADO:
 6. POST comment to ADO API
 7. Update work item state/fields
 
-Display: Bidirectional sync summary"
+Display: Two-way sync summary"
 ```
 
 ---
 
 ## Example Output
 
-### Bidirectional Sync (Default)
+### Two-way Sync (Default)
 
 ```
-🔄 Bidirectional sync for increment 0005...
+🔄 Two-way sync for increment 0005...
 
 ✓ Azure DevOps work item: #12345
-✓ Sync direction: bidirectional (two-way)
+✓ Sync direction: Two-way (push & pull)
 
 Detecting changes (both directions)...
 

package/plugins/specweave-ado/lib/ado-multi-project-sync.js

@@ -373,7 +373,6 @@ ${userStory.technicalContext}
         return mapping.task || "Task";
       case "Subtask":
         return mapping.task || "Task";
-      // ADO doesn't have subtasks, use Task
       default:
         return "User Story";
     }

package/plugins/specweave-github/agents/github-manager/AGENT.md

@@ -38,7 +38,7 @@ GitHub issues MUST use living docs format:
 
 **Tools**: Read, Write, Edit, Bash (GitHub CLI)
 
-**Default Behavior**: **Bidirectional sync** (two-way) - Synchronizes changes in both directions automatically
+**Default Behavior**: **Two-way sync** (push & pull) - Synchronizes changes in both directions automatically
 
 ---
 
@@ -69,8 +69,8 @@ Task({
 
 As the GitHub Manager agent, I specialize in:
 
-### 1. Bidirectional Synchronization (Default)
-- **Two-Way Sync**: Keep SpecWeave and GitHub synchronized automatically
+### 1. Two-way Synchronization (Default)
+- **Two-way Sync**: Keep SpecWeave and GitHub synchronized automatically
   - **FROM GitHub**: Pull status changes, labels, comments, state updates
   - **TO GitHub**: Push task completion, progress updates, metadata
 - **Conflict Resolution**: Detect and resolve conflicts between systems
@@ -79,7 +79,7 @@ As the GitHub Manager agent, I specialize in:
 
 ### 2. Issue Management
 - **Create Issues**: Generate well-formatted GitHub issues from increment specs
-- **Update Issues**: Sync progress, add comments, update labels (bidirectional)
+- **Update Issues**: Sync progress, add comments, update labels (two-way)
 - **Close Issues**: Close issues with completion summaries
 - **Link Issues**: Connect related issues, PRs, and increments
 - **Bulk Operations**: Batch create/update/close issues
@@ -87,7 +87,7 @@ As the GitHub Manager agent, I specialize in:
 ### 3. Progress Tracking
 - **Task Checklists**: Generate and update task checklists in issues
 - **Progress Comments**: Post detailed task completion comments
-- **Status Updates**: Bidirectional sync of increment status ↔ GitHub issue state
+- **Status Updates**: Two-way sync of increment status ↔ GitHub issue state
 - **Time Tracking**: Track estimated vs actual time per task
 - **Milestone Progress**: Update milestone completion percentages
 

package/plugins/specweave-github/commands/specweave-github-sync.md

@@ -83,7 +83,7 @@ Synchronize the current state of a SpecWeave increment with its GitHub issue acr
 - `--comment`: Post progress comment (default)
 - `--labels`: Update issue labels based on status
 - `--force`: Force sync even if up-to-date
-- `--direction`: Sync direction (`to-github`, `from-github`, `bidirectional` - **default: bidirectional**)
+- `--direction`: Sync direction (`to-github`, `from-github`, `two-way` - **default: two-way**)
 - `--all`: Sync all active increments
 
 ### Safety Options
@@ -92,17 +92,17 @@ Synchronize the current state of a SpecWeave increment with its GitHub issue acr
 
 ## Sync Direction
 
-**Default: Bidirectional** (two-way sync)
+**Default: Two-way** (both directions)
 
 SpecWeave syncs changes in **both directions** by default:
 
 | Direction | What It Does | Use When |
 |-----------|-------------|----------|
-| **`bidirectional`** (default) | SpecWeave ↔ GitHub<br>• Pull changes FROM GitHub (status, labels, comments)<br>• Push changes TO GitHub (tasks, progress, metadata) | **Always** (recommended for keeping both systems in sync) |
+| **`two-way`** (default) | SpecWeave ↔ GitHub<br>• Pull changes FROM GitHub (status, labels, comments)<br>• Push changes TO GitHub (tasks, progress, metadata) | **Always** (recommended for keeping both systems in sync) |
 | `to-github` | SpecWeave → GitHub only<br>• Push increment progress to GitHub<br>• Don't pull GitHub changes back | Read-only GitHub usage, or when GitHub is downstream |
 | `from-github` | GitHub → SpecWeave only<br>• Pull GitHub issue updates<br>• Don't push SpecWeave changes | Importing GitHub issues, or when SpecWeave is downstream |
 
-**Why Bidirectional?**
+**Why Two-way?**
 - ✅ Keep both systems synchronized automatically
 - ✅ GitHub status changes update SpecWeave (closed issue → completed increment)
 - ✅ SpecWeave task completion updates GitHub (task done → checklist updated)
@@ -121,16 +121,16 @@ SpecWeave syncs changes in **both directions** by default:
 ## Examples
 
 ```bash
-# Interactive bidirectional sync (default - two-way)
+# Interactive two-way sync (default - both directions)
 /specweave-github:sync 0004
 
-# Use specific profile (still bidirectional by default)
+# Use specific profile (still two-way by default)
 /specweave-github:sync 0004 --profile specweave-dev
 
-# Specify time range (bidirectional)
+# Specify time range (two-way)
 /specweave-github:sync 0004 --time-range 1M
 
-# Full bidirectional sync with all options
+# Full two-way sync with all options
 /specweave-github:sync 0004 --profile main --time-range 1M --tasks --labels
 
 # One-way sync examples (override default)
@@ -140,7 +140,7 @@ SpecWeave syncs changes in **both directions** by default:
 # Dry run to preview changes
 /specweave-github:sync 0004 --dry-run
 
-# Force sync all increments (bidirectional)
+# Force sync all increments (two-way)
 /specweave-github:sync --all --force
 ```
 
@@ -240,12 +240,12 @@ Continue with sync? [Y/n]:
 If confirmed, sync proceeds with progress updates:
 
 ```
-🔄 Bidirectional sync for increment 0004...
+🔄 Two-way sync for increment 0004...
 
 ✓ Profile loaded: specweave-dev
 ✓ GitHub repository: anton-abyzov/specweave
 ✓ Rate limit check: PASSED (4,850/5,000 remaining)
-✓ Sync direction: bidirectional (two-way)
+✓ Sync direction: Two-way (push & pull)
 
 Fetching increment state...
 ✓ Increment loaded: 0004-plugin-architecture
@@ -277,7 +277,7 @@ Syncing FROM GitHub...
 
 Rate limit after sync: 4,570/5,000 (91% available)
 
-✅ Bidirectional Sync Complete!
+✅ Two-way Sync Complete!
 
    SpecWeave ↔ GitHub synchronized
    • Pushed: 3 task updates, progress comment

package/plugins/specweave-github/commands/specweave-github-update-user-story.md

@@ -111,7 +111,7 @@ Progress: 3/6 tasks complete (50%)
 **Related Commands**:
 - `/specweave-github:sync-epic FS-031` - Sync entire epic (all user stories)
 - `/specweave-github:create-issue 0031` - Create issue for increment
-- `/specweave-github:sync 0031` - Bidirectional sync for increment
+- `/specweave-github:sync 0031` - Two-way sync for increment
 
 ---
 

package/plugins/specweave-github/skills/github-sync/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: github-sync
-description: Bidirectional synchronization between SpecWeave specs and GitHub Projects (two-way sync by default). Activates ONLY when user asks questions about GitHub integration or needs help configuring GitHub sync. Does NOT activate for slash commands. For syncing, use /specweave-github:sync-spec command instead.
+description: Two-way synchronization between SpecWeave specs and GitHub Projects (push & pull by default). Activates ONLY when user asks questions about GitHub integration or needs help configuring GitHub sync. Does NOT activate for slash commands. For syncing, use /specweave-github:sync-spec command instead.
 ---
 
-# GitHub Sync - Bidirectional Spec ↔ Project Synchronization
+# GitHub Sync - Two-way Spec ↔ Project Synchronization
 
 **Purpose**: Seamlessly synchronize SpecWeave specs with GitHub Projects for team visibility and project management.
 
-**Default Behavior**: **Bidirectional (two-way) sync** - Changes in either system are automatically synchronized
+**Default Behavior**: **Two-way sync** (push & pull) - Changes in either system are automatically synchronized
 
 **⚠️ IMPORTANT**: This skill provides HELP and GUIDANCE about GitHub sync. For actual syncing, users should use the `/specweave-github:sync-spec` command directly. This skill should NOT auto-activate when the command is being invoked.
 
@@ -203,7 +203,7 @@ Configure GitHub sync in `.specweave/config.json`:
       "specweave-github": {
         "repo": "owner/repo",
         "autoSyncSpecs": true,
-        "syncDirection": "bidirectional",
+        "syncDirection": "two-way",
         "defaultLabels": ["specweave", "spec"],
         "syncFrequency": "on-change"
       }

package/plugins/specweave-jira/commands/specweave-jira-sync.md

@@ -1,6 +1,6 @@
 ---
 name: specweave-jira:sync
-description: Sync SpecWeave increments with JIRA epics/stories. Supports import, export, bidirectional sync, and granular item operations
+description: Sync SpecWeave increments with JIRA epics/stories. Supports import, export, two-way sync, and granular item operations
 ---
 
 # Sync Jira Command
@@ -11,10 +11,10 @@ You are a Jira synchronization expert. Help the user sync between Jira and SpecW
 
 ### Epic-Level Operations
 
-**1. Bidirectional Sync (Default - Recommended)**
+**1. Two-way Sync (Default - Recommended)**
 ```
 /specweave-jira:sync 0003                    # Two-way sync (default)
-/specweave-jira:sync 0003 --direction bidirectional  # Explicit
+/specweave-jira:sync 0003 --direction two-way  # Explicit
 ```
 
 **2. Import Jira Epic as SpecWeave Increment**
@@ -31,9 +31,9 @@ You are a Jira synchronization expert. Help the user sync between Jira and SpecW
 
 ### Sync Direction Options
 
-**Default: `bidirectional`** (two-way sync - recommended)
+**Default: `two-way`** (both directions - recommended)
 
-- `--direction bidirectional`: SpecWeave ↔ Jira (default)
+- `--direction two-way`: SpecWeave ↔ Jira (default)
   - Pull changes FROM Jira (status, priority, comments)
   - Push changes TO Jira (tasks, progress, metadata)
 
@@ -175,7 +175,7 @@ When the user runs this command:
   | Task  | SCRUM-7  | Setup provider  |
   ```
 
-### Example 5: Bidirectional Sync (Default)
+### Example 5: Two-way Sync (Default)
 **User**: `/specweave-jira:sync 0003`
 **You**:
 - Read increment 0003
@@ -186,9 +186,9 @@ When the user runs this command:
 - FROM Jira: Status changes, priority updates, comments
 - FROM SpecWeave: Task completion, progress updates
 
-**Show bidirectional sync summary**:
+**Show two-way sync summary**:
 ```
-✅ Bidirectional Sync Complete: 0003 ↔ Jira
+✅ Two-way Sync Complete: 0003 ↔ Jira
 
 FROM Jira:
   • SCRUM-1: Status changed to In Progress
@@ -204,7 +204,7 @@ Conflicts: None
 **Handle conflicts if any**:
 - Show both versions (Jira vs SpecWeave)
 - Ask user which to keep or how to merge
-- Apply resolution bidirectionally
+- Apply resolution in both directions
 
 ### Example 6: Status Overview
 **User**: `/specweave-jira:sync status`
@@ -229,12 +229,12 @@ Conflicts: None
 
 ## Related Commands
 
-- `/specweave-github:sync` - Sync to GitHub issues (also bidirectional by default)
+- `/specweave-github:sync` - Sync to GitHub issues (also two-way by default)
 - `/specweave:increment` - Create new increment
 - `/specweave:validate` - Validate increment quality
 
 ---
 
-**Bidirectional by Default**: All sync operations are two-way unless you explicitly specify `--direction to-jira` or `--direction from-jira`. This keeps both systems synchronized automatically.
+**Two-way by Default**: All sync operations are two-way unless you explicitly specify `--direction to-jira` or `--direction from-jira`. This keeps both systems synchronized automatically.
 
 **Granular Control**: Unlike simple epic import/export, this command supports cherry-picking individual stories, bugs, and tasks for maximum flexibility.

package/plugins/specweave-jira/lib/enhanced-jira-sync.js

@@ -1,6 +1,6 @@
-import { EnhancedContentBuilder } from "../../../dist/src/core/sync/enhanced-content-builder.js";
-import { SpecIncrementMapper } from "../../../dist/src/core/sync/spec-increment-mapper.js";
-import { parseSpecContent } from "../../../dist/src/core/spec-content-sync.js";
+import { EnhancedContentBuilder } from "../../../src/core/sync/enhanced-content-builder.js";
+import { SpecIncrementMapper } from "../../../src/core/sync/spec-increment-mapper.js";
+import { parseSpecContent } from "../../../src/core/spec-content-sync.js";
 import * as path from "path";
 import * as fs from "fs/promises";
 async function syncSpecToJiraWithEnhancedContent(options) {

package/plugins/specweave-jira/skills/specweave-jira-mapper/SKILL.md

@@ -328,7 +328,7 @@ JIRA Epic: PROJ-123
    ```yaml
    jira:
      last_sync: "2025-10-26T16:30:00Z"
-     sync_direction: "bidirectional"
+     sync_direction: "two-way"
      conflicts_resolved: 2
    ```
 
@@ -336,7 +336,7 @@ JIRA Epic: PROJ-123
 ```
 ✅ Synced with JIRA!
 
-Direction: Bidirectional
+Direction: Two-way
 Changes Applied:
   - SpecWeave → JIRA: 3 updates
   - JIRA → SpecWeave: 5 updates

package/plugins/specweave-release/commands/specweave-release-npm.md

@@ -1,6 +1,6 @@
 ---
 name: specweave-release:npm
-description: Bump patch version, create git tag, and trigger npm publish via GitHub Actions. Automates the complete release workflow with pre-flight checks, version bumping, tag creation, and GitHub Actions triggering. Use --only flag for quick local release (bumps version, builds, publishes to npm directly - NO git push, NO pipeline). Add --push to --only for complete local release with git sync.
+description: Bump patch version, create git tag, and trigger npm publish via GitHub Actions. Automates the complete release workflow with pre-flight checks, version bumping, tag creation, and GitHub Actions triggering. Use --only flag for quick local release (bumps version, builds, publishes to npm directly - NO git push, NO pipeline). Add --push to --only for complete local release with git sync. Use --only --local for FASTEST local-only version bump (no npm publish, no git, just version increment for local testing).
 ---
 
 # /specweave-release:npm - NPM Release Automation
@@ -14,22 +14,27 @@ You are the NPM Release Assistant. Your job is to automate the patch version rel
 | `/specweave-release:npm` | Bump → Push → **CI publishes** | Standard release (CI handles npm) |
 | `/specweave-release:npm --only` | Bump → Build → **Publish locally** → NO push | Quick local release, push later |
 | `/specweave-release:npm --only --push` | Bump → Build → **Publish locally** → Push | Complete local release + git sync |
+| `/specweave-release:npm --only --local` | **Bump ONLY** → NO build, NO publish, NO git | FASTEST: Local testing only |
 
 ## Detecting Mode
 
 Check flags in the command invocation:
 
 ```
---only         → Direct publish to npm (bypass CI)
+--only --local → Version bump ONLY (no build, no publish, no git) - FASTEST
 --only --push  → Direct publish + push to git after
+--only         → Direct publish to npm (bypass CI)
 (no flags)     → Default: push to git, CI publishes
 ```
 
 **Flag Detection Order:**
 1. Check for `--only` flag
-2. If `--only` present, check for `--push` flag
-3. Route to appropriate workflow section
+2. If `--only` present, check for `--local` flag → LOCAL MODE (fastest)
+3. If `--only` present, check for `--push` flag → DIRECT MODE + PUSH
+4. If `--only` only → DIRECT MODE
+5. No flags → DEFAULT MODE
 
+**If `--only --local`**: Use LOCAL MODE (section "Local Mode Workflow") - FASTEST!
 **If `--only --push`**: Use DIRECT MODE WITH PUSH (section "Direct Mode + Push Workflow")
 **If `--only` only**: Use DIRECT MODE (section "Direct Mode Workflow")
 **If no flags**: Use DEFAULT MODE (continue with steps below)
@@ -400,6 +405,9 @@ Show the user:
 
 # Complete local release (publish + push)
 /specweave-release:npm --only --push
+
+# FASTEST: Version bump only (no publish, no git, no build)
+/specweave-release:npm --only --local
 ```
 
 | Scenario | Command | NPM Published By | Git Pushed |
@@ -407,3 +415,85 @@ Show the user:
 | Normal release | (no flags) | GitHub Actions | ✅ Yes |
 | Quick local, push later | `--only` | You (local) | ❌ No |
 | Complete local release | `--only --push` | You (local) | ✅ Yes |
+| **FASTEST local test** | `--only --local` | ❌ None | ❌ No |
+
+---
+
+## LOCAL MODE WORKFLOW (--only --local flags) - FASTEST!
+
+Use this workflow when BOTH `--only` AND `--local` flags are detected. This is the **fastest possible** version bump - NO npm publish, NO git operations, NO build. Just increment the version number for local testing.
+
+**Use case**: You need to quickly test a new version locally without publishing anywhere. Perfect for:
+- Testing version-dependent features
+- Local development iterations
+- Quick version bumps before a real release
+
+### 1. Minimal Pre-flight Check
+
+```bash
+# Just verify current version (no git checks needed!)
+node -p "require('./package.json').version"
+```
+
+**NO git checks** - we're not committing or pushing anything!
+
+### 2. Bump Version (NO git commit, NO tag)
+
+```bash
+# Bump version WITHOUT creating git commit or tag
+npm version patch --no-git-tag-version
+```
+
+**What this does**:
+- Updates `package.json` version ONLY
+- Updates `package-lock.json` version ONLY
+- NO git commit created
+- NO git tag created
+- INSTANT (< 1 second)
+
+### 3. Report Results (Local Mode)
+
+Show the user:
+```markdown
+⚡ **FAST local version bump!**
+
+📦 **Version**: X.Y.Z → X.Y.(Z+1)
+
+**What happened**:
+- ✅ package.json version bumped
+- ✅ package-lock.json updated
+- ⏭️ NO git commit (use `git add . && git commit` later)
+- ⏭️ NO git tag (use `git tag vX.Y.Z` later)
+- ⏭️ NO npm publish (use `npm publish` later)
+- ⏭️ NO build (use `npm run rebuild` later)
+
+**Next steps when ready to release**:
+1. Build: `npm run rebuild`
+2. Test: `npm test`
+3. Commit: `git add . && git commit -m "chore: bump version to X.Y.Z"`
+4. Tag: `git tag vX.Y.Z`
+5. Publish: `npm publish`
+6. Push: `git push origin develop --follow-tags`
+
+**Or use**: `/specweave-release:npm --only --push` for full release
+```
+
+## Local Mode Safety Rules
+
+- ✅ FASTEST possible - single npm command
+- ✅ NO network operations (no npm publish, no git push)
+- ✅ NO disk-heavy operations (no build)
+- ✅ Safe to run multiple times (just increments version)
+- ⚠️ Remember: version is NOT published or committed!
+- ⚠️ Run `npm run rebuild` before testing locally
+
+## Success Criteria (Local Mode)
+
+✅ Version bumped in package.json
+✅ Version bumped in package-lock.json
+⏭️ NO git commit
+⏭️ NO git tag
+⏭️ NO npm publish
+⏭️ NO build
+
+**Time**: < 1 second

package/plugins/specweave/hooks/docs-changed.sh.backup

@@ -1,79 +0,0 @@
-#!/bin/bash
-
-# SpecWeave Docs-Changed Hook
-# Runs after file changes are detected
-# Detects if documentation was changed during implementation
-# Triggers review workflow if needed
-
-set -e
-
-# Find project root by searching upward for .specweave/ directory
-# Works regardless of where hook is installed (source or .claude/hooks/)
-find_project_root() {
-  local dir="$1"
-  while [ "$dir" != "/" ]; do
-    if [ -d "$dir/.specweave" ]; then
-      echo "$dir"
-      return 0
-    fi
-    dir="$(dirname "$dir")"
-  done
-  # Fallback: try current directory
-  if [ -d "$(pwd)/.specweave" ]; then
-    pwd
-  else
-    echo "$(pwd)"
-  fi
-}
-
-PROJECT_ROOT="$(find_project_root "$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)")"
-cd "$PROJECT_ROOT"
-
-# Colors
-RED='\033[0;31m'
-YELLOW='\033[1;33m'
-NC='\033[0m'
-
-# Get changed files (git)
-if ! git rev-parse --git-dir > /dev/null 2>&1; then
-  # Not a git repository, skip
-  exit 0
-fi
-
-CHANGED_FILES=$(git diff --name-only HEAD 2>/dev/null || echo "")
-
-if [ -z "$CHANGED_FILES" ]; then
-  # No changes
-  exit 0
-fi
-
-# Check if any documentation files changed
-DOC_CHANGES=$(echo "$CHANGED_FILES" | grep -E '\.specweave/(docs|increments/.*/.*\.md)' || true)
-
-if [ -n "$DOC_CHANGES" ]; then
-  echo -e "${RED}⚠️  Documentation changed during implementation${NC}"
-  echo ""
-  echo "📋 Files changed:"
-  echo "$DOC_CHANGES" | sed 's/^/   /'
-  echo ""
-  echo -e "${YELLOW}🔔 Recommended actions:${NC}"
-  echo "  1. Review documentation changes"
-  echo "  2. Update tasks.md if architecture changed"
-  echo "  3. Type /review-docs to see full impact"
-  echo ""
-
-  # Play notification sound
-  case "$(uname -s)" in
-    Darwin)
-      afplay /System/Library/Sounds/Ping.aiff 2>/dev/null &
-      ;;
-    Linux)
-      paplay /usr/share/sounds/freedesktop/stereo/dialog-warning.oga 2>/dev/null || true
-      ;;
-  esac
-
-  # Log to hooks log
-  LOGS_DIR=".specweave/logs"
-  mkdir -p "$LOGS_DIR"
-  echo "[$(date)] Documentation changed: $DOC_CHANGES" >> "$LOGS_DIR/hooks.log"
-fi

package/plugins/specweave/hooks/human-input-required.sh.backup

@@ -1,75 +0,0 @@
-#!/bin/bash
-
-# SpecWeave Human-Input-Required Hook
-# Runs when Claude needs clarification or approval
-#
-# Actions:
-# 1. Play notification sound (Ping.aiff)
-# 2. Log the question/requirement
-# 3. Record in current increment's work log (if applicable)
-
-set -e
-
-# Find project root by searching upward for .specweave/ directory
-# Works regardless of where hook is installed (source or .claude/hooks/)
-find_project_root() {
-  local dir="$1"
-  while [ "$dir" != "/" ]; do
-    if [ -d "$dir/.specweave" ]; then
-      echo "$dir"
-      return 0
-    fi
-    dir="$(dirname "$dir")"
-  done
-  # Fallback: try current directory
-  if [ -d "$(pwd)/.specweave" ]; then
-    pwd
-  else
-    echo "$(pwd)"
-  fi
-}
-
-PROJECT_ROOT="$(find_project_root "$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)")"
-cd "$PROJECT_ROOT"
-
-# Get question/requirement (passed as argument or default)
-QUESTION="${1:-User input required}"
-
-echo "❓ Human input required"
-
-# 1. Play notification sound (cross-platform)
-play_sound() {
-  case "$(uname -s)" in
-    Darwin)
-      afplay /System/Library/Sounds/Ping.aiff 2>/dev/null &
-      ;;
-    Linux)
-      paplay /usr/share/sounds/freedesktop/stereo/dialog-question.oga 2>/dev/null || \
-      aplay /usr/share/sounds/alsa/Side_Left.wav 2>/dev/null || true
-      ;;
-    MINGW*|MSYS*|CYGWIN*)
-      powershell -c "(New-Object Media.SoundPlayer 'C:\Windows\Media\notify.wav').PlaySync();" 2>/dev/null || true
-      ;;
-  esac
-}
-
-play_sound &
-
-# 2. Log to main hooks log
-LOGS_DIR=".specweave/logs"
-mkdir -p "$LOGS_DIR"
-echo "[$(date)] Human input required: $QUESTION" >> "$LOGS_DIR/hooks.log"
-
-# 3. Log to current work context (if exists)
-CURRENT_WORK=$(find .specweave/work -maxdepth 1 -type d -name "current-*" | head -1 || true)
-
-if [ -n "$CURRENT_WORK" ] && [ -d "$CURRENT_WORK" ]; then
-    echo "" >> "$CURRENT_WORK/notes.md"
-    echo "## Input Required ($(date +%Y-%m-%d\ %H:%M))" >> "$CURRENT_WORK/notes.md"
-    echo "" >> "$CURRENT_WORK/notes.md"
-    echo "$QUESTION" >> "$CURRENT_WORK/notes.md"
-    echo "" >> "$CURRENT_WORK/notes.md"
-    echo "📝 Logged to $CURRENT_WORK/notes.md"
-fi
-
-echo "✅ Hook complete"