vibe-forge 0.3.0 → 0.3.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/commands/forge.md +35 -26
- package/bin/forge-spawn.sh +2 -2
- package/package.json +1 -1
|
@@ -18,45 +18,51 @@ Based on the first argument, do ONE of the following:
|
|
|
18
18
|
You are now the **Vibe Forge Planning Hub** - a multi-expert planning team.
|
|
19
19
|
|
|
20
20
|
#### Your Identity
|
|
21
|
+
|
|
21
22
|
@_vibe-forge/agents/planning-hub/personality.md
|
|
22
23
|
|
|
23
24
|
#### Project Context
|
|
25
|
+
|
|
24
26
|
@context/project-context.md
|
|
25
27
|
|
|
26
28
|
#### Current Forge State
|
|
29
|
+
|
|
27
30
|
@_vibe-forge/context/forge-state.yaml
|
|
28
31
|
|
|
29
32
|
#### Task Overview
|
|
30
|
-
Pending tasks:
|
|
31
|
-
!`ls _vibe-forge/tasks/pending/ 2>/dev/null || echo "None"`
|
|
32
33
|
|
|
33
|
-
|
|
34
|
-
!`ls _vibe-forge/tasks/in-progress/ 2>/dev/null || echo "None"`
|
|
34
|
+
Check the task folders for current work:
|
|
35
35
|
|
|
36
|
-
Tasks
|
|
37
|
-
|
|
36
|
+
- `_vibe-forge/tasks/pending/` - Tasks waiting to be picked up
|
|
37
|
+
- `_vibe-forge/tasks/in-progress/` - Tasks currently being worked on
|
|
38
|
+
- `_vibe-forge/tasks/needs-changes/` - Tasks that need revision
|
|
38
39
|
|
|
39
|
-
**Startup:** Display the team assembly welcome as shown in your personality's Startup Behavior section. Show the forge council assembling, then check current work status.
|
|
40
|
+
**Startup:** Display the team assembly welcome as shown in your personality's Startup Behavior section. Show the forge council assembling, then use the Glob tool to check for .md files in the task folders above and report the current work status.
|
|
40
41
|
|
|
41
42
|
---
|
|
42
43
|
|
|
43
44
|
### If `$1` is "status" → Show Status Dashboard
|
|
44
45
|
|
|
45
|
-
Display a formatted status dashboard
|
|
46
|
+
Display a formatted status dashboard.
|
|
46
47
|
|
|
47
48
|
#### Forge State
|
|
49
|
+
|
|
48
50
|
@_vibe-forge/context/forge-state.yaml
|
|
49
51
|
|
|
50
52
|
#### Task Counts
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
53
|
+
|
|
54
|
+
Use the Glob tool to count .md files in each task folder:
|
|
55
|
+
|
|
56
|
+
- `_vibe-forge/tasks/pending/*.md` - Pending
|
|
57
|
+
- `_vibe-forge/tasks/in-progress/*.md` - In Progress
|
|
58
|
+
- `_vibe-forge/tasks/completed/*.md` - Completed
|
|
59
|
+
- `_vibe-forge/tasks/review/*.md` - In Review
|
|
60
|
+
- `_vibe-forge/tasks/needs-changes/*.md` - Needs Changes
|
|
61
|
+
- `_vibe-forge/tasks/approved/*.md` - Approved
|
|
57
62
|
|
|
58
63
|
Format output like:
|
|
59
|
-
|
|
64
|
+
|
|
65
|
+
```text
|
|
60
66
|
🔥 VIBE FORGE - Status Dashboard
|
|
61
67
|
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
62
68
|
[Task counts and state summary]
|
|
@@ -71,16 +77,16 @@ Format output like:
|
|
|
71
77
|
|
|
72
78
|
Available agents (with aliases):
|
|
73
79
|
|
|
74
|
-
| Agent
|
|
75
|
-
|
|
76
|
-
| anvil
|
|
77
|
-
| furnace
|
|
78
|
-
| crucible | test, testing, qa
|
|
79
|
-
| sentinel | review, reviewer, cr | Code Reviewer
|
|
80
|
-
| scribe
|
|
81
|
-
| herald
|
|
82
|
-
| ember
|
|
83
|
-
| aegis
|
|
80
|
+
| Agent | Aliases | Role |
|
|
81
|
+
| -------- | -------------------- | ----------------- |
|
|
82
|
+
| anvil | frontend, ui, fe | Frontend Developer |
|
|
83
|
+
| furnace | backend, api, be | Backend Developer |
|
|
84
|
+
| crucible | test, testing, qa | Tester / QA |
|
|
85
|
+
| sentinel | review, reviewer, cr | Code Reviewer |
|
|
86
|
+
| scribe | docs, documentation | Documentation |
|
|
87
|
+
| herald | release, deploy | Release Manager |
|
|
88
|
+
| ember | devops, ops, infra | DevOps |
|
|
89
|
+
| aegis | security, sec, appsec | Security |
|
|
84
90
|
|
|
85
91
|
If `$2` is empty, show the table above and ask which agent to spawn.
|
|
86
92
|
|
|
@@ -99,12 +105,15 @@ Confirm the spawn. If an alias was used (e.g., "frontend"), mention the resolved
|
|
|
99
105
|
**Task description:** `$2` `$3` `$4` (remaining arguments)
|
|
100
106
|
|
|
101
107
|
#### Task Template
|
|
108
|
+
|
|
102
109
|
@_vibe-forge/config/task-template.md
|
|
103
110
|
|
|
104
111
|
#### Existing Tasks
|
|
105
|
-
|
|
112
|
+
|
|
113
|
+
Use the Glob tool to list files in `_vibe-forge/tasks/pending/*.md`
|
|
106
114
|
|
|
107
115
|
If no description provided, ask:
|
|
116
|
+
|
|
108
117
|
- What needs to be done?
|
|
109
118
|
- Which agent? (anvil, furnace, crucible, sentinel, scribe, herald, ember, aegis)
|
|
110
119
|
- Priority? (high, medium, low)
|
package/bin/forge-spawn.sh
CHANGED
|
@@ -52,9 +52,9 @@ spawn_windows_terminal() {
|
|
|
52
52
|
# SECURITY: $agent has already been validated through resolve_agent
|
|
53
53
|
if [[ -n "$GIT_BASH_PATH" ]]; then
|
|
54
54
|
local bash_path="${GIT_BASH_PATH//\//\\}"
|
|
55
|
-
wt.exe new-tab --title "$display_name" "$bash_path" -c "cd '$FORGE_ROOT' && ./bin/forge.sh start '$agent'"
|
|
55
|
+
wt.exe -w 0 new-tab --title "$display_name" "$bash_path" -c "cd '$FORGE_ROOT' && ./bin/forge.sh start '$agent'"
|
|
56
56
|
else
|
|
57
|
-
wt.exe new-tab --title "$display_name" bash -c "cd '$FORGE_ROOT' && ./bin/forge.sh start '$agent'"
|
|
57
|
+
wt.exe -w 0 new-tab --title "$display_name" bash -c "cd '$FORGE_ROOT' && ./bin/forge.sh start '$agent'"
|
|
58
58
|
fi
|
|
59
59
|
log_success "$display_name spawned in new Windows Terminal tab"
|
|
60
60
|
else
|