vibe-forge 0.4.0 → 0.8.1

package/.claude/commands/forge.md

@@ -1,171 +1,218 @@
----
-description: Vibe Forge - multi-agent development orchestration
-argument-hint: [status|spawn <agent>|task [desc]|help]
----
-
-# Vibe Forge Command Router
-
-**Command:** `/forge $ARGUMENTS`
-
-## Route the Command
-
-Based on the first argument, do ONE of the following:
-
----
-
-### If `$1` is empty OR `$1` is "plan" → Start Planning Hub
-
-You are now the **Vibe Forge Planning Hub** - a multi-expert planning team.
-
-#### Your Identity
-
-@_vibe-forge/agents/planning-hub/personality.md
-
-#### Project Context
-
-@context/project-context.md
-
-#### Modern Tooling Reference (avoid outdated suggestions)
-
-@_vibe-forge/context/modern-conventions.md
-
-**Startup:** Display the team assembly welcome:
-
-```text
-🔥 VIBE FORGE - Planning Hub
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-The forge council assembles...
-
-  🔥 Forge Master  - Orchestration & Tasks
-  🏛️ Architect     - Technical Design
-  🛡️ Aegis         - Security
-  ⚙️ Ember         - DevOps & Infrastructure
-  🎨 Pixel         - User Experience
-  📊 Oracle        - Product & Requirements
-  🧪 Crucible      - Quality & Testing
-
-Ready to plan, review, or coordinate.
-Use /forge status to check current tasks.
-
-What's on the anvil today?
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-Do NOT automatically scan task folders - wait for user to ask or use `/forge status`.
-
----
-
-### If `$1` is "status" → Show Status Dashboard
-
-Display a formatted status dashboard.
-
-#### Forge State
-
-@_vibe-forge/context/forge-state.yaml
-
-#### Task Counts
-
-Use the Glob tool to count .md files in each task folder:
-
-- `_vibe-forge/tasks/pending/*.md` - Pending
-- `_vibe-forge/tasks/in-progress/*.md` - In Progress
-- `_vibe-forge/tasks/completed/*.md` - Completed
-- `_vibe-forge/tasks/review/*.md` - In Review
-- `_vibe-forge/tasks/needs-changes/*.md` - Needs Changes
-- `_vibe-forge/tasks/approved/*.md` - Approved
-
-Format output like:
-
-```text
-🔥 VIBE FORGE - Status Dashboard
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-[Task counts and state summary]
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
----
-
-### If `$1` is "spawn" → Spawn Worker Agent
-
-**Agent requested:** `$2`
-
-Available agents (with aliases):
-
-| Agent    | Aliases              | Role              |
-| -------- | -------------------- | ----------------- |
-| anvil    | frontend, ui, fe     | Frontend Developer |
-| furnace  | backend, api, be     | Backend Developer |
-| crucible | test, testing, qa    | Tester / QA       |
-| sentinel | review, reviewer, cr | Code Reviewer     |
-| scribe   | docs, documentation  | Documentation     |
-| herald   | release, deploy      | Release Manager   |
-| ember    | devops, ops, infra   | DevOps            |
-| aegis    | security, sec, appsec | Security         |
-
-If `$2` is empty, show the table above and ask which agent to spawn.
-
-If `$2` is provided, run:
-
-```bash
-./_vibe-forge/bin/forge-spawn.sh $2
-```
-
-Confirm the spawn. If an alias was used (e.g., "frontend"), mention the resolved name: "Spawning **Anvil** (frontend)..."
-
----
-
-### If `$1` is "task" → Create Task
-
-**Task description:** `$2` `$3` `$4` (remaining arguments)
-
-#### Task Template
-
-@_vibe-forge/config/task-template.md
-
-#### Existing Tasks
-
-Use the Glob tool to list files in `_vibe-forge/tasks/pending/*.md`
-
-If no description provided, ask:
-
-- What needs to be done?
-- Which agent? (anvil, furnace, crucible, sentinel, scribe, herald, ember, aegis)
-- Priority? (high, medium, low)
-
-Generate task ID as `task-XXX` (next sequential number), create file at `_vibe-forge/tasks/pending/task-XXX.md`.
-
----
-
-### If `$1` is "help" → Show Help
-
-Display:
-
-```text
-🔥 VIBE FORGE - Commands
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-/forge              Start the Planning Hub (default)
-/forge status       Show status dashboard
-/forge spawn <agent> Spawn worker in new terminal
-/forge task [desc]  Create a new task
-/forge help         Show this help
-
-Agents (with aliases):
-  anvil     (frontend, ui, fe)      - Frontend Developer
-  furnace   (backend, api, be)      - Backend Developer
-  crucible  (test, testing, qa)     - Tester / QA
-  sentinel  (review, reviewer, cr)  - Code Reviewer
-  scribe    (docs, documentation)   - Documentation
-  herald    (release, deploy)       - Release Manager
-  ember     (devops, ops, infra)    - DevOps
-  aegis     (security, sec, appsec) - Security
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
----
-
-### Otherwise → Unknown Command
-
-Tell the user: "Unknown command: $1. Run `/forge help` for available commands."
+---
+description: Vibe Forge - multi-agent development orchestration
+argument-hint: [status|spawn <agent>|task [desc]|redteam [scope]|help]
+---
+
+# Vibe Forge Command Router
+
+**Command:** `/forge $ARGUMENTS`
+
+## Route the Command
+
+Based on the first argument, do ONE of the following:
+
+---
+
+### If `$1` is empty OR `$1` is "plan" → Start Planning Hub
+
+You are now the **Vibe Forge Planning Hub** - a multi-expert planning team.
+
+#### Your Identity
+
+@_vibe-forge/agents/planning-hub/personality.md
+
+#### Project Context
+
+@context/project-context.md
+
+#### Modern Tooling Reference (avoid outdated suggestions)
+
+@_vibe-forge/context/modern-conventions.md
+
+**Startup:** Display the team assembly welcome:
+
+```text
+🔥 VIBE FORGE - Planning Hub
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+The forge council assembles...
+
+  🔥 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.
+
+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
+
+Display a formatted status dashboard.
+
+#### Forge State
+
+@_vibe-forge/context/forge-state.yaml
+
+#### Task Counts
+
+Use the Glob tool to count .md files in each task folder:
+
+- `_vibe-forge/tasks/pending/*.md` - Pending
+- `_vibe-forge/tasks/in-progress/*.md` - In Progress
+- `_vibe-forge/tasks/completed/*.md` - Completed
+- `_vibe-forge/tasks/review/*.md` - In Review
+- `_vibe-forge/tasks/needs-changes/*.md` - Needs Changes
+- `_vibe-forge/tasks/approved/*.md` - Approved
+
+Format output like:
+
+```text
+🔥 VIBE FORGE - Status Dashboard
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+[Task counts and state summary]
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+---
+
+### If `$1` is "spawn" → Spawn Worker Agent
+
+**Agent requested:** `$2`
+
+Available agents (with aliases):
+
+| Agent    | Aliases              | Role              |
+| -------- | -------------------- | ----------------- |
+| anvil    | frontend, ui, fe     | Frontend Developer |
+| furnace  | backend, api, be     | Backend Developer |
+| crucible | test, testing, qa    | Tester / QA       |
+| sentinel | review, reviewer, cr | Code Reviewer     |
+| scribe   | docs, documentation  | Documentation     |
+| 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.
+
+If `$2` is provided, run:
+
+```bash
+./_vibe-forge/bin/forge-spawn.sh $2
+```
+
+Confirm the spawn. If an alias was used (e.g., "frontend"), mention the resolved name: "Spawning **Anvil** (frontend)..."
+
+---
+
+### If `$1` is "task" → Create Task
+
+**Task description:** `$2` `$3` `$4` (remaining arguments)
+
+#### Task Template
+
+@_vibe-forge/config/task-template.md
+
+#### Existing Tasks
+
+Use the Glob tool to list files in `_vibe-forge/tasks/pending/*.md`
+
+If no description provided, ask:
+
+- What needs to be done?
+- Which agent? (anvil, furnace, crucible, sentinel, scribe, herald, ember, aegis)
+- Priority? (high, medium, low)
+
+Generate task ID as `task-XXX` (next sequential number), create file at `_vibe-forge/tasks/pending/task-XXX.md`.
+
+---
+
+### If `$1` is "help" → Show Help
+
+Display:
+
+```text
+🔥 VIBE FORGE - Commands
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+/forge              Start the Planning Hub (default)
+/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):
+  anvil     (frontend, ui, fe)      - Frontend Developer
+  furnace   (backend, api, be)      - Backend Developer
+  crucible  (test, testing, qa)     - Tester / QA
+  sentinel  (review, reviewer, cr)  - Code Reviewer
+  scribe    (docs, documentation)   - Documentation
+  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.