@only1btayy/g2w 1.0.21 → 1.0.24
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/README.md +23 -0
- package/package.json +1 -1
- package/skills/ready2save.md +19 -8
package/README.md
CHANGED
|
@@ -108,6 +108,22 @@ The plan is the contract. By the time The Builder touches a single line of code,
|
|
|
108
108
|
|
|
109
109
|
---
|
|
110
110
|
|
|
111
|
+
### Optional Methods
|
|
112
|
+
|
|
113
|
+
Each Foundation agent is also a direct slash command. The normal flow runs through `/g2w:build2gether` and `/g2w:get2work` — but if you know what you're doing, you can jump straight into any stage of the pipeline.
|
|
114
|
+
|
|
115
|
+
| Command | When to use it directly |
|
|
116
|
+
|---|---|
|
|
117
|
+
| `/g2w:the-visionary` | You have a half-written plan and just want it finished — skip the full build2gether flow |
|
|
118
|
+
| `/g2w:the-challenger` | You wrote your own plan outside G2W and want it stress-tested before building |
|
|
119
|
+
| `/g2w:the-builder` | Plan is already locked — skip straight to building |
|
|
120
|
+
| `/g2w:the-inspector` | Code is already written — just verify it against a plan |
|
|
121
|
+
| `/g2w:the-leader` | Kick off the full pipeline without the identity, brainstorm, and research phases |
|
|
122
|
+
|
|
123
|
+
These are escape hatches for engineers who don't need the ceremony. G2W has no ceiling.
|
|
124
|
+
|
|
125
|
+
---
|
|
126
|
+
|
|
111
127
|
### The Trust Layer
|
|
112
128
|
|
|
113
129
|
Delivered via hook so it runs every single session, not just when the AI remembers.
|
|
@@ -199,4 +215,11 @@ Under active development. First real-world test case is Blackhole VST running th
|
|
|
199
215
|
|
|
200
216
|
---
|
|
201
217
|
|
|
218
|
+
## Acknowledgements
|
|
219
|
+
|
|
220
|
+
- **[johnkf5-ops/the-dev-squad](https://github.com/johnkf5-ops/the-dev-squad)** — inspired The Foundation's multi-agent pipeline
|
|
221
|
+
- **John Knopf** — modular doc system approach. His words: *"Take it, run with it, use it, modify it, make it better. That's the whole point."*
|
|
222
|
+
|
|
223
|
+
---
|
|
224
|
+
|
|
202
225
|
*Built by ONLY1BTAYY · MIT License · Claude Code native*
|
package/package.json
CHANGED
package/skills/ready2save.md
CHANGED
|
@@ -9,14 +9,19 @@ You are closing out this session. Leave the project in a state where any future
|
|
|
9
9
|
|
|
10
10
|
## Steps
|
|
11
11
|
|
|
12
|
-
1. **
|
|
12
|
+
1. **Capture decisions** — Review the conversation history and extract:
|
|
13
|
+
- What was built or changed
|
|
14
|
+
- Key decisions made and the reasoning behind them
|
|
15
|
+
- Any "don't do this again" lessons learned
|
|
13
16
|
|
|
14
|
-
|
|
15
|
-
> "What key decisions did we make this session that future-me needs to know? (reasoning behind choices, not just what was done)"
|
|
17
|
+
Do NOT ask the user to recall this — you have the full conversation. Only ask if something is genuinely ambiguous.
|
|
16
18
|
|
|
17
|
-
|
|
19
|
+
2. **Confirm the active project** — List all folders inside `projects/` and ask:
|
|
20
|
+
> "Which project are we saving? (pick one)"
|
|
18
21
|
|
|
19
|
-
|
|
22
|
+
Wait for the user to confirm. Do not assume based on what was discussed — the user decides.
|
|
23
|
+
|
|
24
|
+
3. **Update `.g2w/CURRENT.md`** in the confirmed project folder with exactly three sections:
|
|
20
25
|
```
|
|
21
26
|
## Last Completed
|
|
22
27
|
[What was finished and verified this session — be specific]
|
|
@@ -28,13 +33,19 @@ You are closing out this session. Leave the project in a state where any future
|
|
|
28
33
|
[The single most important next task]
|
|
29
34
|
```
|
|
30
35
|
|
|
31
|
-
|
|
36
|
+
Then write (or overwrite) `.g2w/CURRENT.md` in the **`Claudes Brain` root** with a single line:
|
|
37
|
+
```
|
|
38
|
+
active: projects/[confirmed-project-folder-name]
|
|
39
|
+
```
|
|
40
|
+
This is the pointer `back2it` uses to find the right project next session.
|
|
41
|
+
|
|
42
|
+
4. **Write a handoff note** at the bottom of `.g2w/CURRENT.md` under `## Session Notes — [date]`:
|
|
32
43
|
- What was built
|
|
33
44
|
- Key decisions made AND the reasoning behind them (the WHY matters more than the WHAT)
|
|
34
45
|
- Any gotchas or "don't do this again" lessons
|
|
35
46
|
- What to read first next session
|
|
36
47
|
|
|
37
|
-
4b. **Mine into MemPalace (if installed):** Run `/
|
|
48
|
+
4b. **Mine into MemPalace (if installed):** Run `/mempalace:mine` on the project's `.g2w/CURRENT.md` to index this session's decisions into MemPalace. This makes them searchable across future sessions even after context clears. If MemPalace isn't installed, skip this step silently.
|
|
38
49
|
|
|
39
50
|
5. **Commit** everything that was verified this session:
|
|
40
51
|
```
|
|
@@ -54,5 +65,5 @@ You are closing out this session. Leave the project in a state where any future
|
|
|
54
65
|
|
|
55
66
|
- Never commit unverified work — if something wasn't tested, say so and don't include it
|
|
56
67
|
- The handoff note must capture WHY decisions were made, not just what was done
|
|
57
|
-
-
|
|
68
|
+
- Extract decisions from the conversation — never make the user recall work you already witnessed
|
|
58
69
|
- Do not clear context or close anything — that's the user's call
|