vibe-forge 0.3.12 → 0.8.1

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

@@ -0,0 +1,102 @@
+---
+description: Configure or re-detect version control system settings
+argument-hint: [detect|set <type>]
+---
+
+# Configure VCS Command
+
+Configure or re-detect the version control system for this project. This affects how agents handle branching, PRs, and CI workflows.
+
+## Usage
+
+```
+/configure-vcs                  # Interactive configuration
+/configure-vcs detect           # Auto-detect from project structure
+/configure-vcs set github       # Manually set to GitHub
+/configure-vcs set gitlab       # Manually set to GitLab
+/configure-vcs set gitea        # Manually set to Gitea (self-hosted)
+/configure-vcs set azure-devops # Manually set to Azure DevOps
+/configure-vcs set bitbucket    # Manually set to Bitbucket
+/configure-vcs set git-only     # Git without platform
+/configure-vcs set none         # No version control
+```
+
+## Supported Platforms
+
+| Type | Platform | PR Command | CI Config |
+|------|----------|------------|-----------|
+| `github` | GitHub | `gh pr create` | `.github/workflows/` |
+| `gitlab` | GitLab | `git push -o merge_request.create` | `.gitlab-ci.yml` |
+| `gitea` | Gitea/Codeberg | `tea pr create` | `.gitea/workflows/` |
+| `azure-devops` | Azure DevOps | `az repos pr create` | `azure-pipelines.yml` |
+| `bitbucket` | Bitbucket | Manual via UI | `bitbucket-pipelines.yml` |
+| `git-only` | Git (no platform) | N/A | N/A |
+| `none` | No VCS | N/A | N/A |
+
+## Implementation
+
+Based on `$ARGUMENTS`:
+
+### If no arguments (interactive mode):
+
+1. Run detection: `node bin/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
+5. Report configuration saved
+
+### If `detect`:
+
+1. Run: `node bin/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
+
+### 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>`
+3. Report folders created (if any)
+4. Confirm configuration saved
+
+## Detection Logic
+
+The VCS detector checks (in order of priority):
+
+1. **Platform folders**: `.github/`, `.gitlab/`, `.gitea/`, `.azure/`
+2. **CI config files**: `.gitlab-ci.yml`, `azure-pipelines.yml`, `bitbucket-pipelines.yml`
+3. **Git remote URL**: Parses `.git/config` for github.com, gitlab.com, gitea, codeberg.org, etc.
+4. **Fallback**: `git-only` if `.git/` exists, `none` otherwise
+
+## Impact on Agents
+
+When VCS is configured, agents will:
+
+- **github**: Use `gh pr create`, reference GitHub Actions
+- **gitlab**: Use merge request workflow, reference GitLab CI
+- **azure-devops**: Use `az repos pr create`, reference Azure Pipelines
+- **bitbucket**: Provide manual PR instructions, reference Bitbucket Pipelines
+- **git-only**: Use branch workflow without PR commands
+- **none**: Skip all git-related instructions
+
+## Configuration File
+
+VCS config is stored in `.forge/config.json`:
+
+```json
+{
+  "vcs": {
+    "type": "github",
+    "name": "GitHub",
+    "autoDetected": false,
+    "lastUpdated": "2026-01-16T12:00:00Z"
+  }
+}
+```
+
+## When to Use
+
+- **Initial setup**: Automatically run during `forge init`
+- **Adding git later**: Run `/configure-vcs detect` after `git init`
+- **Switching platforms**: Run `/configure-vcs set <type>` when migrating
+- **Troubleshooting**: Run `/configure-vcs` if agents give wrong git instructions

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