vibe-forge 0.3.12 → 0.8.1

package/.claude/commands/need-help.md

@@ -1,77 +1,77 @@
----
-description: Signal that you need human attention/input
-argument-hint: <brief reason>
----
-
-# Need Help Command
-
-Use this command when you're blocked and need human input. This will:
-
-1. Create an attention file in `tasks/attention/`
-2. Ring the terminal bell for immediate notification
-3. Trigger a system toast notification (if daemon is running)
-4. Show in the Planning Hub's status display
-
-## Usage
-
-```
-/need-help Need clarification on auth implementation approach
-/need-help Blocked on API design decision - REST vs GraphQL?
-/need-help Tests failing, need guidance on expected behavior
-```
-
-## Implementation
-
-Based on `$ARGUMENTS`:
-
-1. Determine your agent identity from your system prompt or context
-2. Create an attention file at `tasks/attention/<agent>-<timestamp>.md`:
-
-```markdown
----
-agent: <your-agent-name>
-created: <ISO timestamp>
-status: pending
----
-
-# Attention Needed
-
-**Agent:** <icon> <display-name>
-**Time:** <human-readable time>
-
-## Issue
-
-$ARGUMENTS
-
-## Context
-
-<Brief context about what you were working on>
-```
-
-3. Ring the terminal bell:
-
-```bash
-printf '\a'
-```
-
-4. Announce that you've signaled for help and will wait.
-
-## Resolving Attention
-
-When a human responds (via Hub or directly), they can:
-- Delete the attention file to clear the flag
-- Move it to a resolved folder
-- Or just respond - the worker can delete their own attention file once unblocked
-
-## Example Output
-
-After running `/need-help Need decision on caching strategy`:
-
-```
-🔔 Attention signal sent!
-
-I've created tasks/attention/anvil-20240115-143022.md
-The Planning Hub and daemon have been notified.
-
-I'll wait for guidance. You can respond here or via the Hub.
-```
+---
+description: Signal that you need human attention/input
+argument-hint: <brief reason>
+---
+
+# Need Help Command
+
+Use this command when you're blocked and need human input. This will:
+
+1. Create an attention file in `tasks/attention/`
+2. Ring the terminal bell for immediate notification
+3. Trigger a system toast notification (if daemon is running)
+4. Show in the Planning Hub's status display
+
+## Usage
+
+```
+/need-help Need clarification on auth implementation approach
+/need-help Blocked on API design decision - REST vs GraphQL?
+/need-help Tests failing, need guidance on expected behavior
+```
+
+## Implementation
+
+Based on `$ARGUMENTS`:
+
+1. Determine your agent identity from your system prompt or context
+2. Create an attention file at `tasks/attention/<agent>-<timestamp>.md`:
+
+```markdown
+---
+agent: <your-agent-name>
+created: <ISO timestamp>
+status: pending
+---
+
+# Attention Needed
+
+**Agent:** <icon> <display-name>
+**Time:** <human-readable time>
+
+## Issue
+
+$ARGUMENTS
+
+## Context
+
+<Brief context about what you were working on>
+```
+
+3. Ring the terminal bell:
+
+```bash
+printf '\a'
+```
+
+4. Announce that you've signaled for help and will wait.
+
+## Resolving Attention
+
+When a human responds (via Hub or directly), they can:
+- Delete the attention file to clear the flag
+- Move it to a resolved folder
+- Or just respond - the worker can delete their own attention file once unblocked
+
+## Example Output
+
+After running `/need-help Need decision on caching strategy`:
+
+```
+🔔 Attention signal sent!
+
+I've created tasks/attention/anvil-20240115-143022.md
+The Planning Hub and daemon have been notified.
+
+I'll wait for guidance. You can respond here or via the Hub.
+```

package/.claude/commands/update-status.md

@@ -1,64 +1,64 @@
----
-description: Update your agent status for the forge dashboard
-argument-hint: <status> [task-id]
----
-
-# Update Status Command
-
-Report your current status to the forge daemon and Planning Hub. This enables real-time visibility into what each worker is doing.
-
-## Usage
-
-```
-/update-status working TASK-001       # Working on a specific task
-/update-status idle                   # Waiting for tasks
-/update-status blocked                # Stuck, may need help
-/update-status reviewing PR-123       # Reviewing something
-/update-status testing TASK-001       # Running tests
-```
-
-## Status Values
-
-| Status | Meaning |
-|--------|---------|
-| `idle` | No current task, ready for work |
-| `working` | Actively working on a task |
-| `blocked` | Stuck, needs input (consider `/need-help`) |
-| `reviewing` | Reviewing code or PR |
-| `testing` | Running tests |
-| `waiting` | Waiting for external dependency |
-
-## Implementation
-
-Based on `$ARGUMENTS`:
-
-1. Parse the status and optional task ID from arguments
-2. Determine your agent identity from your system prompt
-3. Write status file to `context/agent-status/<agent>.json`:
-
-```json
-{
-  "agent": "anvil",
-  "status": "working",
-  "task": "TASK-001",
-  "message": "Implementing user authentication",
-  "updated": "2024-01-15T14:30:22Z"
-}
-```
-
-4. The daemon reads these files and includes them in `forge-state.yaml`
-5. The Planning Hub sees your status in the dashboard
-
-## Auto-Status Updates
-
-Workers should update their status at these key moments:
-
-1. **On startup**: `/update-status idle` (or working if picking up a task)
-2. **When picking up a task**: `/update-status working TASK-XXX`
-3. **When completing a task**: `/update-status idle`
-4. **When blocked**: `/update-status blocked` (then `/need-help` if needed)
-5. **Before exiting**: Status file can remain (daemon marks stale after timeout)
-
-## Stale Status
-
-The daemon considers a status stale if not updated for 5+ minutes. Stale statuses are shown with a warning indicator in the dashboard.
+---
+description: Update your agent status for the forge dashboard
+argument-hint: <status> [task-id]
+---
+
+# Update Status Command
+
+Report your current status to the forge daemon and Planning Hub. This enables real-time visibility into what each worker is doing.
+
+## Usage
+
+```
+/update-status working TASK-001       # Working on a specific task
+/update-status idle                   # Waiting for tasks
+/update-status blocked                # Stuck, may need help
+/update-status reviewing PR-123       # Reviewing something
+/update-status testing TASK-001       # Running tests
+```
+
+## Status Values
+
+| Status | Meaning |
+|--------|---------|
+| `idle` | No current task, ready for work |
+| `working` | Actively working on a task |
+| `blocked` | Stuck, needs input (consider `/need-help`) |
+| `reviewing` | Reviewing code or PR |
+| `testing` | Running tests |
+| `waiting` | Waiting for external dependency |
+
+## Implementation
+
+Based on `$ARGUMENTS`:
+
+1. Parse the status and optional task ID from arguments
+2. Determine your agent identity from your system prompt
+3. Write status file to `context/agent-status/<agent>.json`:
+
+```json
+{
+  "agent": "anvil",
+  "status": "working",
+  "task": "TASK-001",
+  "message": "Implementing user authentication",
+  "updated": "2026-01-15T14:30:22Z"  // ISO 8601 timestamp (auto-generated)
+}
+```
+
+4. The daemon reads these files and includes them in `forge-state.yaml`
+5. The Planning Hub sees your status in the dashboard
+
+## Auto-Status Updates
+
+Workers should update their status at these key moments:
+
+1. **On startup**: `/update-status idle` (or working if picking up a task)
+2. **When picking up a task**: `/update-status working TASK-XXX`
+3. **When completing a task**: `/update-status idle`
+4. **When blocked**: `/update-status blocked` (then `/need-help` if needed)
+5. **Before exiting**: Status file can remain (daemon marks stale after timeout)
+
+## Stale Status
+
+The daemon considers a status stale if not updated for 5+ minutes. Stale statuses are shown with a warning indicator in the dashboard.

package/.claude/commands/worker-loop.md

@@ -1,106 +1,106 @@
----
-description: Start a persistent worker loop (Ralph-style)
-argument-hint: <agent> [--max-idle 10] | stop
----
-
-# Worker Loop Command
-
-Start a persistent worker loop for the specified agent. The worker will:
-1. Check for assigned tasks
-2. Work on tasks until complete
-3. Loop back and check for more tasks
-4. Only exit after N idle checks with no work found
-
-## Activation Modes
-
-Worker Loop can be activated in two ways:
-
-### 1. Config-based (Recommended)
-
-Enable during `forge init` or toggle anytime:
-
-```bash
-forge config worker-loop on     # Enable for all workers
-forge config worker-loop off    # Disable
-forge config worker-loop        # Check status
-```
-
-When enabled, ALL workers will automatically stay running and check for new tasks.
-
-### 2. Runtime (Per-session)
-
-Use this command for fine-grained control:
-
-```
-/worker-loop anvil              # Start Anvil in persistent loop
-/worker-loop furnace --max-idle 20  # Custom idle limit
-/worker-loop stop               # Stop the current loop
-```
-
-## Arguments
-
-- `$1` - Agent name (anvil, furnace, crucible, etc.) or "stop"
-- `--max-idle N` - Exit after N checks with no tasks (default: 10)
-
-## Implementation
-
-Based on `$ARGUMENTS`:
-
-### If first argument is "stop"
-
-Remove the worker loop state file and confirm:
-
-```bash
-rm -f "${CLAUDE_LOCAL_DIR:-$HOME/.claude}/forge-worker-loop.json"
-```
-
-Output: "Worker loop stopped."
-
-### Otherwise, start a loop
-
-1. Resolve the agent name to canonical form
-2. Create state file at `${CLAUDE_LOCAL_DIR}/forge-worker-loop.json`:
-
-```json
-{
-  "agent": "<resolved-agent>",
-  "max_idle_checks": 10,
-  "idle_count": 0,
-  "poll_interval": 5,
-  "started_at": "<ISO timestamp>"
-}
-```
-
-3. Load the agent's personality file
-4. Start working with this system prompt addition:
-
-```
-You are in PERSISTENT WORKER MODE. After completing each task:
-1. Check for more tasks assigned to you in tasks/pending/ and tasks/needs-changes/
-2. If tasks found, immediately begin working
-3. If no tasks, announce you are idle and waiting
-
-Do NOT ask permission to continue - work autonomously until no tasks remain.
-```
-
-5. The stop hook (hooks/worker-loop.sh) will intercept exit attempts and:
-   - If tasks exist: feed prompt to continue working
-   - If no tasks: increment idle counter
-   - If max idle reached: allow exit
-
-## How It Works
-
-The Worker Loop uses Claude Code's **Stop Hook** feature:
-
-1. When a worker tries to exit, the hook script runs
-2. It checks for pending tasks in `tasks/pending/` and `tasks/needs-changes/`
-3. If tasks found: blocks exit and feeds a prompt to continue working
-4. If no tasks: allows exit (or waits, depending on config)
-
-## Benefits
-
-- Workers stay active and pick up new tasks automatically
-- No need to manually respawn workers
-- Tasks can be added to pending/ and workers will find them
-- Config-based mode requires zero per-session setup
-- Configurable idle timeout prevents infinite waiting
+---
+description: Start a persistent worker loop (Ralph-style)
+argument-hint: <agent> [--max-idle 10] | stop
+---
+
+# Worker Loop Command
+
+Start a persistent worker loop for the specified agent. The worker will:
+1. Check for assigned tasks
+2. Work on tasks until complete
+3. Loop back and check for more tasks
+4. Only exit after N idle checks with no work found
+
+## Activation Modes
+
+Worker Loop can be activated in two ways:
+
+### 1. Config-based (Recommended)
+
+Enable during `forge init` or toggle anytime:
+
+```bash
+forge config worker-loop on     # Enable for all workers
+forge config worker-loop off    # Disable
+forge config worker-loop        # Check status
+```
+
+When enabled, ALL workers will automatically stay running and check for new tasks.
+
+### 2. Runtime (Per-session)
+
+Use this command for fine-grained control:
+
+```
+/worker-loop anvil              # Start Anvil in persistent loop
+/worker-loop furnace --max-idle 20  # Custom idle limit
+/worker-loop stop               # Stop the current loop
+```
+
+## Arguments
+
+- `$1` - Agent name (anvil, furnace, crucible, etc.) or "stop"
+- `--max-idle N` - Exit after N checks with no tasks (default: 10)
+
+## Implementation
+
+Based on `$ARGUMENTS`:
+
+### If first argument is "stop"
+
+Remove the worker loop state file and confirm:
+
+```bash
+rm -f "${CLAUDE_LOCAL_DIR:-$HOME/.claude}/forge-worker-loop.json"
+```
+
+Output: "Worker loop stopped."
+
+### Otherwise, start a loop
+
+1. Resolve the agent name to canonical form
+2. Create state file at `${CLAUDE_LOCAL_DIR}/forge-worker-loop.json`:
+
+```json
+{
+  "agent": "<resolved-agent>",
+  "max_idle_checks": 10,
+  "idle_count": 0,
+  "poll_interval": 5,
+  "started_at": "<ISO timestamp>"
+}
+```
+
+3. Load the agent's personality file
+4. Start working with this system prompt addition:
+
+```
+You are in PERSISTENT WORKER MODE. After completing each task:
+1. Check for more tasks assigned to you in tasks/pending/ and tasks/needs-changes/
+2. If tasks found, immediately begin working
+3. If no tasks, announce you are idle and waiting
+
+Do NOT ask permission to continue - work autonomously until no tasks remain.
+```
+
+5. The stop hook (hooks/worker-loop.js) will intercept exit attempts and:
+   - If tasks exist: feed prompt to continue working
+   - If no tasks: increment idle counter
+   - If max idle reached: allow exit
+
+## How It Works
+
+The Worker Loop uses Claude Code's **Stop Hook** feature:
+
+1. When a worker tries to exit, the hook script runs
+2. It checks for pending tasks in `tasks/pending/` and `tasks/needs-changes/`
+3. If tasks found: blocks exit and feeds a prompt to continue working
+4. If no tasks: allows exit (or waits, depending on config)
+
+## Benefits
+
+- Workers stay active and pick up new tasks automatically
+- No need to manually respawn workers
+- Tasks can be added to pending/ and workers will find them
+- Config-based mode requires zero per-session setup
+- Configurable idle timeout prevents infinite waiting