vibe-forge 0.3.0 → 0.3.1

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.
@@ -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
- In-progress tasks:
34
- !`ls _vibe-forge/tasks/in-progress/ 2>/dev/null || echo "None"`
34
+ Check the task folders for current work:
35
35
 
36
- Tasks needing changes:
37
- !`ls _vibe-forge/tasks/needs-changes/ 2>/dev/null || echo "None"`
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
- !`echo "Pending: $(ls _vibe-forge/tasks/pending/*.md 2>/dev/null | wc -l || echo 0)"`
52
- !`echo "In Progress: $(ls _vibe-forge/tasks/in-progress/*.md 2>/dev/null | wc -l || echo 0)"`
53
- !`echo "Completed: $(ls _vibe-forge/tasks/completed/*.md 2>/dev/null | wc -l || echo 0)"`
54
- !`echo "In Review: $(ls _vibe-forge/tasks/review/*.md 2>/dev/null | wc -l || echo 0)"`
55
- !`echo "Needs Changes: $(ls _vibe-forge/tasks/needs-changes/*.md 2>/dev/null | wc -l || echo 0)"`
56
- !`echo "Approved: $(ls _vibe-forge/tasks/approved/*.md 2>/dev/null | wc -l || echo 0)"`
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 | Aliases | Role |
75
- |-------|---------|------|
76
- | anvil | frontend, ui, fe | Frontend Developer |
77
- | furnace | backend, api, be | Backend Developer |
78
- | crucible | test, testing, qa | Tester / QA |
79
- | sentinel | review, reviewer, cr | Code Reviewer |
80
- | scribe | docs, documentation | Documentation |
81
- | herald | release, deploy | Release Manager |
82
- | ember | devops, ops, infra | DevOps |
83
- | aegis | security, sec, appsec | Security |
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
- !`ls _vibe-forge/tasks/pending/ 2>/dev/null || echo "None pending"`
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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "vibe-forge",
3
- "version": "0.3.0",
3
+ "version": "0.3.1",
4
4
  "description": "Multi-agent development orchestration system for terminal-native vibe coding",
5
5
  "keywords": [
6
6
  "vibe-coding",