vibe-forge 0.4.0 → 0.8.2

package/.claude/commands/clear-attention.md

@@ -1,63 +1,63 @@
----
-description: Clear an attention signal after helping a worker
-argument-hint: [agent-name | all]
----
-
-# Clear Attention Command
-
-Use this command to clear attention signals after you've helped a blocked worker.
-
-## Usage
-
-```
-/clear-attention anvil    # Clear Anvil's attention signal
-/clear-attention all      # Clear all attention signals
-/clear-attention          # List current attention signals
-```
-
-## Implementation
-
-Based on `$ARGUMENTS`:
-
-### If no argument or empty
-
-List all current attention signals from `tasks/attention/`:
-
-```
-🔔 Current Attention Signals:
-
-1. Anvil (5 min ago): Need clarification on auth implementation
-2. Crucible (2 min ago): Tests failing, unsure of expected behavior
-
-Use /clear-attention <agent> to resolve.
-```
-
-### If argument is "all"
-
-Remove all files from `tasks/attention/` and confirm:
-
-```
-✅ Cleared all attention signals (2 resolved)
-```
-
-### If argument is an agent name
-
-1. Find and remove files matching that agent in `tasks/attention/`
-2. Confirm removal:
-
-```
-✅ Cleared attention signal for Anvil
-```
-
-If no matching signal found:
-
-```
-No attention signal found for Anvil
-```
-
-## Notes
-
-- Attention files are created by workers using `/need-help`
-- The daemon watches this folder and sends notifications
-- Clearing signals is a way to acknowledge you've responded
-- Workers can also clear their own signals when unblocked
+---
+description: Clear an attention signal after helping a worker
+argument-hint: [agent-name | all]
+---
+
+# Clear Attention Command
+
+Use this command to clear attention signals after you've helped a blocked worker.
+
+## Usage
+
+```
+/clear-attention anvil    # Clear Anvil's attention signal
+/clear-attention all      # Clear all attention signals
+/clear-attention          # List current attention signals
+```
+
+## Implementation
+
+Based on `$ARGUMENTS`:
+
+### If no argument or empty
+
+List all current attention signals from `tasks/attention/`:
+
+```
+🔔 Current Attention Signals:
+
+1. Anvil (5 min ago): Need clarification on auth implementation
+2. Crucible (2 min ago): Tests failing, unsure of expected behavior
+
+Use /clear-attention <agent> to resolve.
+```
+
+### If argument is "all"
+
+Remove all files from `tasks/attention/` and confirm:
+
+```
+✅ Cleared all attention signals (2 resolved)
+```
+
+### If argument is an agent name
+
+1. Find and remove files matching that agent in `tasks/attention/`
+2. Confirm removal:
+
+```
+✅ Cleared attention signal for Anvil
+```
+
+If no matching signal found:
+
+```
+No attention signal found for Anvil
+```
+
+## Notes
+
+- Attention files are created by workers using `/need-help`
+- The daemon watches this folder and sends notifications
+- Clearing signals is a way to acknowledge you've responded
+- Workers can also clear their own signals when unblocked

package/.claude/commands/compact-context.md

@@ -0,0 +1,52 @@
+# Compact Context
+
+Compress the current conversation to free up context window space while preserving all essential information.
+
+## When to Use
+
+Use this when:
+- You notice response quality degrading (repetitive, forgetting earlier decisions)
+- A task is running long and you want to continue without starting fresh
+- The conversation history is getting unwieldy
+- Before picking up a new task in the same session
+
+## How to Compact
+
+Summarize the current conversation into a dense brief using this format:
+
+```
+## Context Compact — [timestamp]
+
+### Work In Progress
+- Task: [task ID and title]
+- Status: [what's done, what's not]
+- Files touched: [list]
+
+### Key Decisions Made
+- [decision 1 and the reason behind it]
+- [decision 2 and the reason behind it]
+
+### Architecture Constraints Discovered
+- [any patterns, restrictions, or conventions learned from reading code]
+
+### Tests Written
+- [test file: X tests passing]
+
+### Blockers / Open Questions
+- [anything unresolved]
+
+### Next Step
+[Exactly what to do next when work resumes]
+```
+
+After writing the summary, respond with:
+
+> Context compacted. Summary above replaces prior conversation history.
+> Ready to continue with: [next step].
+
+## Rules
+
+- Never lose acceptance criteria state -- list any unchecked ACs explicitly
+- Never lose test counts -- the DoD requires accurate numbers
+- Keep the summary under 400 words -- longer defeats the purpose
+- If mid-task: the summary IS the handoff. Make it complete enough to resume cold.

package/.claude/commands/configure-vcs.md

@@ -39,23 +39,23 @@ Based on `$ARGUMENTS`:
 
 ### If no arguments (interactive mode):
 
-1. Run detection: `node bin/lib/vcs.js detect`
+1. Run detection: `node src/lib/vcs.js detect`
 2. Show current setting and detected type
 3. Ask user to confirm or change
-4. Run `node bin/lib/vcs.js init <type>` to create folders
+4. Run `node src/lib/vcs.js init <type>` to create folders
 5. Report configuration saved
 
 ### If `detect`:
 
-1. Run: `node bin/lib/vcs.js detect`
+1. Run: `node src/lib/vcs.js detect`
 2. Display detected type and confidence
 3. If confident detection, ask to apply
-4. Run `node bin/lib/vcs.js set <type>` to save
+4. Run `node src/lib/vcs.js set <type>` to save
 
 ### If `set <type>`:
 
 1. Validate type is one of: github, gitlab, azure-devops, bitbucket, git-only, none
-2. Run: `node bin/lib/vcs.js init <type>`
+2. Run: `node src/lib/vcs.js init <type>`
 3. Report folders created (if any)
 4. Confirm configuration saved
 

package/.claude/commands/forge.md

@@ -1,6 +1,6 @@
 ---
 description: Vibe Forge - multi-agent development orchestration
-argument-hint: [status|spawn <agent>|task [desc]|help]
+argument-hint: [status|spawn <agent>|task [desc]|redteam [scope]|help]
 ---
 
 # Vibe Forge Command Router
@@ -37,13 +37,14 @@ You are now the **Vibe Forge Planning Hub** - a multi-expert planning team.
 
 The forge council assembles...
 
-  🔥 Forge Master  - Orchestration & Tasks
+  🔥 Planning Hub  - Orchestration & Tasks
   🏛️ Architect     - Technical Design
   🛡️ Aegis         - Security
   ⚙️ Ember         - DevOps & Infrastructure
   🎨 Pixel         - User Experience
   📊 Oracle        - Product & Requirements
   🧪 Crucible      - Quality & Testing
+  🎭 Loki          - Lateral Thinking & Assumption Challenger
 
 Ready to plan, review, or coordinate.
 Use /forge status to check current tasks.
@@ -54,6 +55,8 @@ What's on the anvil today?
 
 Do NOT automatically scan task folders - wait for user to ask or use `/forge status`.
 
+If `$1` is "plan" and `$2+` contains a feature description (e.g., `/forge plan user authentication`), enter **Planning Mode** immediately with the feature as the discovery input. Skip the generic welcome and go straight to Phase 1 (Discovery) with Oracle asking clarifying questions about the described feature.
+
 ---
 
 ### If `$1` is "status" → Show Status Dashboard
@@ -102,6 +105,10 @@ Available agents (with aliases):
 | herald   | release, deploy      | Release Manager   |
 | ember    | devops, ops, infra   | DevOps            |
 | aegis    | security, sec, appsec | Security         |
+| slag     | redteam, pentest      | Red Team Lead    |
+| flux     | infra-sec, chaos      | Red Team Operator |
+| loki     | trickster, lateral    | Lateral Thinker (Planning Hub) |
+| crucible-x | adversarial, break-it, cx | Adversarial Reviewer |
 
 If `$2` is empty, show the table above and ask which agent to spawn.
 
@@ -121,7 +128,7 @@ Confirm the spawn. If an alias was used (e.g., "frontend"), mention the resolved
 
 #### Task Template
 
-@_vibe-forge/config/task-template.md
+@_vibe-forge/templates/task-template.md
 
 #### Existing Tasks
 
@@ -149,6 +156,7 @@ Display:
 /forge status       Show status dashboard
 /forge spawn <agent> Spawn worker in new terminal
 /forge task [desc]  Create a new task
+/forge redteam [scope] Launch red team engagement
 /forge help         Show this help
 
 Agents (with aliases):
@@ -160,12 +168,51 @@ Agents (with aliases):
   herald    (release, deploy)       - Release Manager
   ember     (devops, ops, infra)    - DevOps
   aegis     (security, sec, appsec) - Security
+  slag      (redteam, pentest)     - Red Team Lead
+  flux      (infra-sec, chaos)     - Red Team Operator
+  loki      (trickster, lateral)   - Lateral Thinker (Planning Hub)
+  crucible-x (adversarial, cx)     - Adversarial Reviewer
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
 ---
 
+### If `$1` is "redteam" → Launch Red Team Engagement
+
+**Scope:** `$2` `$3` `$4` (remaining arguments)
+
+If no scope provided, ask:
+- What should the red team target? (e.g., "auth module", "API endpoints", "full application")
+- Any exclusions? (systems/endpoints off-limits)
+- Attack types? (OWASP, infra, supply-chain, all)
+
+Display:
+
+```text
+💀 VIBE FORGE - Red Team Engagement
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Scope: [target]
+Lead: Slag (💀 Offensive Security)
+Operator: Flux (⚡ Infrastructure)
+
+Rules of Engagement:
+  - requires_approval: true (all actions need sign-off)
+  - Separation of duties: no Aegis collaboration during engagement
+  - All findings documented with PoC
+
+Spawning red team...
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+Then run:
+
+```bash
+./_vibe-forge/bin/forge-spawn.sh slag
+```
+
+---
+
 ### Otherwise → Unknown Command
 
 Tell the user: "Unknown command: $1. Run `/forge help` for available commands."

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": "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.
+---
+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.