@only1btayy/g2w 1.0.14 → 1.0.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@only1btayy/g2w",
-  "version": "1.0.14",
+  "version": "1.0.15",
   "description": "G2W — a relationship protocol for building trust with AI",
   "bin": {
     "g2w": "bin/g2w.js"

package/skills/back2it.md

@@ -9,12 +9,16 @@ You are resuming a G2W session. Get back up to speed fast. No fluff.
 
 ## Steps
 
-1. **Read `CURRENT.md`** in the project root. This is your source of truth.
+1. **Find the active project** — Read `.g2w/CURRENT.md` in the `Claudes Brain` root (the top-level working directory).
+   - If it contains a line like `active: projects/[folder]`, read `projects/[folder]/.g2w/CURRENT.md` as your source of truth.
+   - If the root `.g2w/CURRENT.md` is missing or has no `active:` line, say:
+     > "No active project found. Which project were you working on?"
+   - Wait for the user's answer before doing anything else.
 
 2. **Read one supporting doc** based on what's In Progress:
-   - If In Progress involves code structure or a new feature → read `ARCHITECTURE.md`
-   - If In Progress involves a bug or error → read `ERRORS.md`
-   - If In Progress involves writing or modifying code → read `CONVENTIONS.md`
+   - If In Progress involves code structure or a new feature → read `.g2w/ARCHITECTURE.md`
+   - If In Progress involves a bug or error → read `.g2w/ERRORS.md`
+   - If In Progress involves writing or modifying code → read `.g2w/CONVENTIONS.md`
    - If nothing is In Progress → no additional doc needed
 
 3. **Doc integrity check:** Does the doc you read still match the current state? If something looks stale, flag it before touching anything else.
@@ -33,5 +37,5 @@ You are resuming a G2W session. Get back up to speed fast. No fluff.
 
 - Do not read files beyond what's needed for the current task
 - Do not start executing anything — this is orientation only
-- If CURRENT.md is missing or empty, say so and ask the user to describe where things stand
+- If the root `.g2w/CURRENT.md` is missing or has no `active:` line, always ask — never guess
 - If docs look out of sync with the code, fix the doc FIRST before touching anything else

package/skills/bring2life.md

@@ -69,7 +69,7 @@ Fill in the `❓ [UNKNOWN]` gaps based on their answers.
 
 ## Phase 4 — Final Output
 
-Write the completed doc files to the project root.
+Create a `.g2w/` folder in the project root if it doesn't exist. Write all completed doc files there.
 
 Output a summary:
 ```

package/skills/get2work.md

@@ -12,7 +12,7 @@ You are executing a locked plan. Build exactly what it says. Nothing extra. Noth
 1. **Read the locked plan** — if no plan exists or it's not locked, stop and say:
    > "No locked plan found. Run `/g2w:build2gether` first."
 
-2. **Read `CONVENTIONS.md`** — know the rules before touching code.
+2. **Read `.g2w/CONVENTIONS.md`** — know the rules before touching code.
 
 3. **Declare scope** — before writing a single line, output:
    ```

package/skills/ready2save.md

@@ -9,12 +9,14 @@ You are closing out this session. Leave the project in a state where any future
 
 ## Steps
 
-1. **Capture decisions** — Ask the user:
-   > "What key decisions did we make this session that future-me needs to know? (reasoning behind choices, not just what was done)"
+1. **Capture decisions** — Review the conversation history and extract:
+   - What was built or changed
+   - Key decisions made and the reasoning behind them
+   - Any "don't do this again" lessons learned
 
-   Wait for their answer. Do not skip this.
+   Do NOT ask the user to recall this — you have the full conversation. Only ask if something is genuinely ambiguous.
 
-2. **Update `CURRENT.md`** with exactly three sections:
+2. **Update `.g2w/CURRENT.md`** in the current project folder with exactly three sections:
    ```
    ## Last Completed
    [What was finished and verified this session — be specific]
@@ -26,7 +28,13 @@ You are closing out this session. Leave the project in a state where any future
    [The single most important next task]
    ```
 
-3. **Write a handoff note** at the bottom of `CURRENT.md` under `## Session Notes — [date]`:
+   Then write (or overwrite) `.g2w/CURRENT.md` in the **`Claudes Brain` root** with a single line:
+   ```
+   active: projects/[this-project-folder-name]
+   ```
+   This is the pointer `back2it` uses to find the right project next session.
+
+3. **Write a handoff note** at the bottom of `.g2w/CURRENT.md` under `## Session Notes — [date]`:
    - What was built
    - Key decisions made AND the reasoning behind them (the WHY matters more than the WHAT)
    - Any gotchas or "don't do this again" lessons
@@ -50,5 +58,5 @@ You are closing out this session. Leave the project in a state where any future
 
 - Never commit unverified work — if something wasn't tested, say so and don't include it
 - The handoff note must capture WHY decisions were made, not just what was done
-- If the user skips the decisions question, prompt once more — this is the most important part
+- Extract decisions from the conversation — never make the user recall work you already witnessed
 - Do not clear context or close anything — that's the user's call

package/skills/true2dagame.md

@@ -15,7 +15,7 @@ Run each check and record ✅ PASS, ⚠️ WARNING, or ❌ FAIL.
 
 ### 1. Doc Sync Check
 
-For each G2W doc that exists in this project:
+For each G2W doc that exists in `.g2w/`:
 - Does `ARCHITECTURE.md` reflect the current tech stack and structure?
 - Does `FEATURES.md` reflect what's actually built vs what's broken vs what's next?
 - Does `ERRORS.md` list the current known bugs with accurate severity?
@@ -37,7 +37,7 @@ Flag any doc that looks stale or inconsistent with what you can observe.
 
 ### 3. Error Status Check
 
-- Read `ERRORS.md`
+- Read `.g2w/ERRORS.md`
 - Flag any CRITICAL or HIGH severity errors that are unresolved
 - Are any errors listed as "in progress" but stale (no recent activity)?
 
@@ -45,7 +45,7 @@ Flag any doc that looks stale or inconsistent with what you can observe.
 
 ### 4. CURRENT.md Freshness
 
-- Does `CURRENT.md` reflect the last session accurately?
+- Does `.g2w/CURRENT.md` reflect the last session accurately?
 - Is "In Progress" still actually in progress, or was it finished and not updated?
 - Is "Next" still the right next task?
 

package/skills/true2plan.md

@@ -14,7 +14,7 @@ You are the verifier. Your job is not to say "looks good" — it is to confirm t
    - Definition of done
    - Any specific behaviors or outputs promised
 
-2. **Read `TESTING.md`** — run through the checklist for this area.
+2. **Read `.g2w/TESTING.md`** — run through the checklist for this area.
 
 3. **Verify file-by-file:**
 
@@ -56,9 +56,9 @@ You are the verifier. Your job is not to say "looks good" — it is to confirm t
    > "Verification failed. Back to building — [specific issues]."
 
 8. **If PASS** → update docs and hand off:
-   - Update `CHANGELOG.md` with what was built and when
-   - Update `FEATURES.md` if a feature was added
-   - Update `ERRORS.md` if a bug was fixed
+   - Update `.g2w/CHANGELOG.md` with what was built and when
+   - Update `.g2w/FEATURES.md` if a feature was added
+   - Update `.g2w/ERRORS.md` if a bug was fixed
    - Then: "Verified. Run `/g2w:ready2save` to commit and close out."
 
 ## Rules