@only1btayy/g2w 1.0.10 → 1.0.12

package/README.md

@@ -24,11 +24,7 @@ This is not a workflow system. Not a task runner. This is a protocol for buildin
 ---
 
 ```bash
-npm install -g @only1btayy/g2w
-```
-
-```
-✅ G2W installed at ~/.claude/ — 9 skills + hooks ready.
+npm install -g @only1btayy/g2w && g2w
 ```
 
 **Works on Mac, Windows, and Linux.**

package/lib/install.js

@@ -4,14 +4,16 @@ const os = require('os');
 const { LOGO } = require('./logo');
 
 function writeTTY(text) {
+  // Plain stderr first — npm shows this reliably
+  const plain = text.replace(/\x1b\[[0-9;]*m/g, '');
+  process.stderr.write(plain);
+  // Then try CONOUT$ for the colored version
   try {
     const devName = process.platform === 'win32' ? 'CONOUT$' : '/dev/tty';
     const fd = fs.openSync(devName, 'w');
     fs.writeSync(fd, text);
     fs.closeSync(fd);
-  } catch {
-    process.stderr.write(text);
-  }
+  } catch {}
 }
 const SKILLS_SRC = path.join(__dirname, '../skills');
 

package/package.json

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

package/skills/build2gether.md

@@ -37,7 +37,7 @@ Once requirements are locked and research is complete:
 **Planner Agent** writes a complete plan:
 - No placeholders. Actual code, actual file names, actual decisions.
 - Declares exactly which files will be created or modified — nothing undeclared
-- Writes a concrete definition of done for this specific task
+- Writes a definition of done tied to the user's actual environment — not "it compiled." Specific steps: what build to run, what to open, what to click, what the exact expected result is. If you can't describe how to verify it in the user's setup, the definition of done is not done.
 - Estimates scope honestly: small / medium / large
 
 **Reviewer Agent** does an adversarial pass: