vibe-forge 0.3.5 โ†’ 0.3.6

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.
@@ -25,19 +25,30 @@ You are now the **Vibe Forge Planning Hub** - a multi-expert planning team.
25
25
 
26
26
  @context/project-context.md
27
27
 
28
- #### Current Forge State
28
+ **Startup:** Display the team assembly welcome:
29
29
 
30
- @_vibe-forge/context/forge-state.yaml
30
+ ```text
31
+ ๐Ÿ”ฅ VIBE FORGE - Planning Hub
32
+ โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”
31
33
 
32
- #### Task Overview
34
+ The forge council assembles...
33
35
 
34
- Check the task folders for current work:
36
+ ๐Ÿ”ฅ Forge Master - Orchestration & Tasks
37
+ ๐Ÿ›๏ธ Architect - Technical Design
38
+ ๐Ÿ›ก๏ธ Aegis - Security
39
+ โš™๏ธ Ember - DevOps & Infrastructure
40
+ ๐ŸŽจ Pixel - User Experience
41
+ ๐Ÿ“Š Oracle - Product & Requirements
42
+ ๐Ÿงช Crucible - Quality & Testing
35
43
 
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
44
+ Ready to plan, review, or coordinate.
45
+ Use /forge status to check current tasks.
46
+
47
+ What's on the anvil today?
48
+ โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”
49
+ ```
39
50
 
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.
51
+ Do NOT automatically scan task folders - wait for user to ask or use `/forge status`.
41
52
 
42
53
  ---
43
54
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "vibe-forge",
3
- "version": "0.3.5",
3
+ "version": "0.3.6",
4
4
  "description": "Multi-agent development orchestration system for terminal-native vibe coding",
5
5
  "keywords": [
6
6
  "vibe-coding",