@veleads/gtm 0.2.0 → 0.3.0

package/kit/skills/05-copy/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: 05-copy
-description: Stage 5 of the gtm-brain process. Writes the email sequence and personalization per segment × persona and signal angle in copy.md, grounded in personas, offer, approved proof and voice. Ends at a hard stop for client copy sign-off.
+description: Stage 5 of the gtm-brain process. Writes the email sequence and personalization per segment × persona and signal angle in copy.md, grounded in personas, offer, approved proof and voice. Ends at a hard stop for copy sign-off by the project approver.
 ---
 
 # 05 · Copy
 
 ## Purpose
 Write messages the target persona would actually reply to, using only facts
-the client approved.
+the approver signed off.
 
 ## Inputs
 - `context/personas.md`, `offer.md`, `proof.md` (only "approved for outbound: yes"), `voice.md`
@@ -27,9 +27,9 @@ the client approved.
    a variable.
 5. Self-review against the checklist below, then render each step once with a fictional example
    lead (fictional name and company) for the human.
-6. **HARD STOP.** Present all variants for client sign-off. Edits requested → change, re-present,
+6. **HARD STOP.** Present all variants for sign-off. Edits requested → change, re-present,
    still pending. Only after explicit approval from the named approver, record it:
-   `pnpm gtm approve copy <campaign> --by "<Name (client)>" --notes "<what was approved>"`. Quote the
+   `npx gtm approve copy <campaign> --by "<Name (role)>" --notes "<what was approved>"`. Quote the
    approval in the run log and commit `copy.md`, `config.yaml` and the run log together.
 
 ## Outputs
@@ -45,8 +45,8 @@ the client approved.
 - [ ] Plain-text friendly; at most one link, none in step 1 preferred
 
 ## Gate
-**Client copy sign-off (hard stop).** Recorded with `pnpm gtm approve copy <campaign>`, which pins a
-hash of `copy.md`. Any later change to the copy makes `pnpm gtm validate` fail and blocks the campaign
+**Copy sign-off (hard stop).** Recorded with `npx gtm approve copy <campaign>`, which pins a
+hash of `copy.md`. Any later change to the copy makes `npx gtm validate` fail and blocks the campaign
 past `copy` until it is re-approved (or the change is reverted). Note lines starting with `>` (status,
 available variables) and whitespace-only changes do not count.
 

package/kit/skills/06-qa/SKILL.md

@@ -13,8 +13,8 @@ Catch every avoidable problem before a single email is sent. QA is a checklist,
 - `.gtm/templates/outputs/qa-report.md`
 
 ## Steps
-1. `pnpm gtm validate <campaign>` must pass.
-2. `pnpm gtm job qa <campaign>`: validates every lead in send tiers against the `Lead` schema
+1. `npx gtm validate <campaign>` must pass.
+2. `npx gtm job qa <campaign>`: validates every lead in send tiers against the `Lead` schema
    (`.gtm/schemas/lead.schema.json`: verified email, allowed tier, suppression checked, `field_sources.email`
    present), checks every copy variable is filled, prints counts and rejection reasons.
 3. Re-run suppression if the last check is older than 24h at planned launch time.

package/kit/skills/07-launch/SKILL.md

@@ -12,15 +12,15 @@ Get the approved leads and copy into the sender safely, and start sending only o
 - `qa.md` (ready: yes), `config.yaml` → `sending`, `gates.copy` (approved), `copy.md`
 
 ## Steps
-1. Verify: `gates.copy.status == approved`, `qa.md` ready, `pnpm gtm validate` passes. Otherwise stop.
-2. `pnpm gtm job push <campaign>`: creates the sender campaign **paused**, uploads the
+1. Verify: `gates.copy.status == approved`, `qa.md` ready, `npx gtm validate` passes. Otherwise stop.
+2. `npx gtm job push <campaign>`: creates the sender campaign **paused**, uploads the
    sequence from `copy.md`, pushes leads in send tiers, sets the schedule from `sending`. Write the
    returned reference into `config.yaml` → `sending.sender_campaign_ref`.
 3. Read the push counts: accepted vs. rejected (with reasons). Rejections > 2% → investigate first.
 4. **HARD STOP: go/no-go.** Present: leads pushed by tier, daily volume and ramp, first send
    date/time, spend so far vs. cap, QA summary, sender campaign ref (paused). Ask the campaign owner
    or GTM engineer for an explicit go. Record in `config.yaml` → `gates.launch` per AGENTS.md section 4.
-5. Only after approval: `pnpm gtm job activate <campaign>`. Set `stage: results`.
+5. Only after approval: `npx gtm job activate <campaign>`. Set `stage: results`.
 6. Run log: push counts, who approved, exact time activated.
 
 ## Outputs

package/kit/skills/08-results/SKILL.md

@@ -12,7 +12,7 @@ Know what is working by segment × variant, protect deliverability, and feed lea
 - `config.yaml` → `sending.sender_campaign_ref`; `brief.md` success metrics
 
 ## Steps
-1. `pnpm gtm job results <campaign>`: pulls events since the last pull into `outreach_events`,
+1. `npx gtm job results <campaign>`: pulls events since the last pull into `outreach_events`,
    updates lead statuses, adds bounces/unsubscribes to suppression, prints aggregates by
    segment × variant × step.
 2. Health check first: bounce rate > 3% or any spam complaints → mandatory stop; recommend pausing
@@ -22,7 +22,7 @@ Know what is working by segment × variant, protect deliverability, and feed lea
 4. Write the run log (counts only). Weekly: `reports/<YYYY-Www>.md` from `.gtm/templates/outputs/weekly-report.md`.
 5. Compare against brief metrics. Recommend changes (variant to pause, segment to expand), but
    copy changes go back through `05-copy` and its gate, and targeting changes through `01-icp`/`04-qualify`.
-6. Learnings that apply beyond this client → "Learnings → PRs" in the run log, then a
+6. Learnings that apply beyond this project → "Learnings → PRs" in the run log, then a
    PR to Veleads/gtm-core editing the relevant skill (never edit `.gtm/` here).
 
 ## Outputs
@@ -36,7 +36,7 @@ Run log per pull; weekly report; suppression updated (DB).
 
 ## Gate
 None (recurring). The campaign ends when the brief's timeframe ends or the human stops it. Write a
-final report and set `client.yaml` status if the engagement ends.
+final report and set `project.yaml` status if the engagement ends.
 
 ## Next
-Next campaign: `pnpm gtm new-campaign <slug>` → routing table.
+Next campaign: `npx gtm new-campaign <slug>` → routing table.

package/kit/templates/campaign/brief.md

@@ -1,6 +1,6 @@
 # Campaign brief: __CAMPAIGN_ID__
 
-- **Client:** __CLIENT_ID__
+- **Project:** __PROJECT_ID__
 - **Campaign id:** __CAMPAIGN_ID__
 - **Branch:** `campaign/__CAMPAIGN_ID__`
 - **Owner:** __OWNER__

package/kit/templates/campaign/config.yaml

@@ -1,10 +1,10 @@
 # yaml-language-server: $schema=../../.gtm/schemas/campaign-config.schema.json
-version: 1
-client_id: __CLIENT_ID__
+version: 2
+project_id: __PROJECT_ID__
 campaign_id: __CAMPAIGN_ID__
 owner: __OWNER__
 stage: icp
-tam_id: __CLIENT_ID__-tam-TODO
+tam_id: __PROJECT_ID__-tam-TODO
 segments: [segment-one]
 personas: [persona-one]
 

package/kit/templates/outputs/qa-report.md

@@ -3,7 +3,7 @@
 > Stage 6 output, saved as campaigns/<campaign>/qa.md. Every box must be checked or explained.
 
 ## 1. Data
-- [ ] `pnpm gtm validate <campaign>` passes
+- [ ] `npx gtm validate <campaign>` passes
 - [ ] Lead export validated against schemas `Lead`: <n> valid / <n> rejected (reasons)
 - [ ] Only send_tiers present; tier counts: A <n> · B <n>
 - [ ] Suppression re-checked within 24h of launch: <n> removed

package/kit/templates/outputs/run-log.md

@@ -2,7 +2,7 @@
 
 > Append-only. One file per run per user: runs/<YYYY-MM-DD>-<user>[-n].md. No PII.
 
-- **Client / campaign:**
+- **Project / campaign:**
 - **Branch / commit:**
 - **Agent:** (Claude Code / Codex / other)
 - **Stage(s) worked:**

package/kit/templates/outputs/weekly-report.md

@@ -1,4 +1,4 @@
-# Weekly report: <client> · week <YYYY-Www>
+# Weekly report: <project> · week <YYYY-Www>
 
 > Saved as campaigns/<campaign>/reports/<YYYY-Www>.md. Aggregates only.
 

package/kit/templates/{client → project}/icp.md

@@ -1,4 +1,4 @@
-# ICP: __CLIENT_NAME__
+# ICP: __PROJECT_NAME__
 
 > Human-readable rationale. The machine-readable version is `icp.yaml`. Keep them in sync.
 

package/kit/templates/{client → project}/icp.yaml

@@ -1,6 +1,6 @@
 # yaml-language-server: $schema=../.gtm/schemas/icp.schema.json
-version: 1
-client_id: __CLIENT_ID__
+version: 2
+project_id: __PROJECT_ID__
 approval:
   status: pending # only a named human approves (AGENTS.md hard stop)
   approved_by: null

package/kit/templates/{client → project}/intake.md

@@ -1,4 +1,4 @@
-# Intake: __CLIENT_NAME__
+# Intake: __PROJECT_NAME__
 
 > Stage 0 output. Fill every section; write "unknown" rather than leaving blanks.
 
@@ -31,13 +31,13 @@
 ## Access checklist
 | Item | Owner | Status |
 |---|---|---|
-| CRM export: customers + open deals (domains only) for suppression | client | |
-| Do-not-contact list | client | |
-| Previously contacted list (last 90 days) | client | |
-| Sending domains purchased | agency | |
-| Inboxes created + warmup started (date) | agency | |
-| Sender workspace created | agency | |
-| Calendar / booking link | client | |
-| Lawful basis documented (LIA for EU/UK legitimate interest) | client + agency | |
-| Privacy notice URL | client | |
-| Named approver for ICP + copy | client | |
+| CRM export: customers + open deals (domains only) for suppression | stakeholder | |
+| Do-not-contact list | stakeholder | |
+| Previously contacted list (last 90 days) | stakeholder | |
+| Sending domains purchased | GTM team | |
+| Inboxes created + warmup started (date) | GTM team | |
+| Sender workspace created | GTM team | |
+| Calendar / booking link | stakeholder | |
+| Lawful basis documented (LIA for EU/UK legitimate interest) | stakeholder + GTM team | |
+| Privacy notice URL | stakeholder | |
+| Named approver for ICP + copy | stakeholder | |

package/kit/templates/{client → project}/offer.md

@@ -1,4 +1,4 @@
-# Offer: __CLIENT_NAME__
+# Offer: __PROJECT_NAME__
 
 - **Core offer:**
 - **Outbound CTA (low friction):**

package/kit/templates/{client → project}/personas.md

@@ -1,4 +1,4 @@
-# Personas: __CLIENT_NAME__
+# Personas: __PROJECT_NAME__
 
 ## <persona-id> (role)
 - **Cares about:**

package/kit/templates/project/project.yaml

@@ -0,0 +1,12 @@
+# yaml-language-server: $schema=.gtm/schemas/project.schema.json
+version: 2
+project_id: __PROJECT_ID__
+name: __PROJECT_NAME__
+status: onboarding
+started_at: __TODAY__
+owners:
+  gtm_engineer: TODO
+  sdrs: []
+  approver: TODO # person who signs off ICP and copy for this project
+regions: [TODO]
+features: {} # opt-in core features (see .gtm/ CHANGELOG / FEATURES)

package/kit/templates/{client → project}/proof.md

@@ -1,4 +1,4 @@
-# Proof: __CLIENT_NAME__
+# Proof: __PROJECT_NAME__
 
 Only items marked **approved for outbound** may appear in copy.
 

package/kit/templates/{client → project}/signals.yaml

@@ -1,6 +1,6 @@
 # yaml-language-server: $schema=../.gtm/schemas/signals.schema.json
-version: 1
-client_id: __CLIENT_ID__
+version: 2
+project_id: __PROJECT_ID__
 signals:
   - key: signal-one
     description: TODO

package/kit/templates/{client → project}/voice.md

@@ -1,4 +1,4 @@
-# Voice: __CLIENT_NAME__
+# Voice: __PROJECT_NAME__
 
 - Language / spelling:
 - Tone:

package/kit/templates/repo/{CLIENT.md → PROJECT.md}

@@ -1,16 +1,16 @@
-# CLIENT.md: __CLIENT_NAME__
+# PROJECT.md: __PROJECT_NAME__
 
-Client-specific rules for agents and people working in this repo. Read after AGENTS.md.
+Project-specific rules for agents and people working in this repo. Read after AGENTS.md.
 
 Rules here may ADD steps or constraints to a stage. They may never remove a step, skip a check,
-or weaken a hard stop from AGENTS.md. If a core rule seems wrong for this client, propose the change
+or weaken a hard stop from AGENTS.md. If a core rule seems wrong for this project, propose the change
 in Veleads/gtm-core instead.
 
 ## Standing constraints
 - (e.g. Never target subsidiaries of X. Legal must review any mention of Y.)
 
 ## Stage additions
-- 05-copy: (e.g. All copy in British English; client wants 2 variants max.)
+- 05-copy: (e.g. All copy in British English; approver wants 2 variants max.)
 
 ## Contacts
-- Client approver: see client.yaml → owners.client_approver
+- Project approver: see project.yaml → owners.approver

package/kit/templates/repo/README.md

@@ -1,24 +1,24 @@
-# gtm-client-__CLIENT_ID__ · __CLIENT_NAME__
+# gtm-project-__PROJECT_ID__ · __PROJECT_NAME__
 
-Private client repo. Runs the standard gtm-brain process from the public core package
+Private project repo. Runs the standard gtm-brain process from the public core package
 [`@veleads/gtm`](https://www.npmjs.com/package/@veleads/gtm), pinned in
-`package.json`. **Start with AGENTS.md** (generated from core; do not edit) and then CLIENT.md.
+`package.json`. **Start with AGENTS.md** (generated from core; do not edit) and then PROJECT.md.
 
 ## Setup
 ```bash
-pnpm install
+npm install          # or: pnpm install / yarn install
 cp .env.example .env
-pnpm gtm status
-pnpm gtm validate
+npx gtm status
+npx gtm validate
 ```
 
 ## What lives where
 | Path | Owner | Edit? |
 |---|---|---|
 | `AGENTS.md`, `.gtm/` | core (`gtm sync`) | never: changes go to Veleads/gtm-core |
-| `CLIENT.md` | this client | yes: client-specific additions only |
-| `client.yaml`, `context/`, `tam/`, `campaigns/` | this client | yes: through the stage playbooks |
+| `PROJECT.md` | this project | yes: project-specific additions only |
+| `project.yaml`, `context/`, `tam/`, `campaigns/` | this project | yes: through the stage playbooks |
 
 ## Core upgrades
 A weekly workflow opens a PR when a new core is released (`.github/workflows/gtm-upgrade.yml`).
-Manually: `pnpm gtm upgrade` (refuses while a campaign is between QA and launch).
+Manually: `npx gtm upgrade` (refuses while a campaign is between QA and launch).

package/kit/templates/repo/github/workflows/gtm-upgrade.yml

@@ -14,19 +14,25 @@ jobs:
       pull-requests: write
     steps:
       - uses: actions/checkout@v7
-      - uses: pnpm/action-setup@v6
       - uses: actions/setup-node@v7
         with:
           node-version: 22
-      - run: pnpm install --frozen-lockfile
+      - name: Install
+        run: |
+          if [ -f pnpm-lock.yaml ]; then npx -y pnpm@10 install --frozen-lockfile
+          elif [ -f yarn.lock ]; then npx -y yarn@1 install --frozen-lockfile
+          elif [ -f package-lock.json ]; then npm ci
+          else npm install
+          fi
       - name: Upgrade core (sync + migrate + validate)
         id: upgrade
         run: |
           before=$(node -p "require('./package.json').devDependencies['@veleads/gtm']")
-          pnpm exec gtm upgrade 2>&1 | tee upgrade.log || true
+          npx gtm upgrade 2>&1 | tee "$RUNNER_TEMP/upgrade.log" || true
           after=$(node -p "require('./package.json').devDependencies['@veleads/gtm']")
           echo "before=$before" >> "$GITHUB_OUTPUT"
           echo "after=$after" >> "$GITHUB_OUTPUT"
+      # Commits every change the upgrade made (kit, AGENTS.md, lockfile, migrated and renamed files).
       - name: Open PR
         if: steps.upgrade.outputs.before != steps.upgrade.outputs.after
         uses: peter-evans/create-pull-request@v8
@@ -34,12 +40,4 @@ jobs:
           branch: upgrade/core-v${{ steps.upgrade.outputs.after }}
           title: "chore: core ${{ steps.upgrade.outputs.before }} → ${{ steps.upgrade.outputs.after }}"
           commit-message: "chore: core v${{ steps.upgrade.outputs.after }}"
-          body-path: upgrade.log
-          add-paths: |
-            package.json
-            pnpm-lock.yaml
-            AGENTS.md
-            .gtm/**
-            client.yaml
-            context/*.yaml
-            campaigns/*/config.yaml
+          body-path: ${{ runner.temp }}/upgrade.log

package/kit/templates/repo/github/workflows/gtm.yml

@@ -4,20 +4,26 @@ on:
   push:
     branches: [main]
 
+permissions:
+  contents: read
+
 jobs:
   check:
     runs-on: ubuntu-latest
-    permissions:
-      contents: read
     steps:
       - uses: actions/checkout@v7
-      - uses: pnpm/action-setup@v6
       - uses: actions/setup-node@v7
         with:
           node-version: 22
-          cache: pnpm
-      - run: pnpm install --frozen-lockfile
+      # Works with whichever package manager this repo uses (detected from the committed lockfile).
+      - name: Install
+        run: |
+          if [ -f pnpm-lock.yaml ]; then npx -y pnpm@10 install --frozen-lockfile
+          elif [ -f yarn.lock ]; then npx -y yarn@1 install --frozen-lockfile
+          elif [ -f package-lock.json ]; then npm ci
+          else npm install
+          fi
       - name: Core files untouched and in sync
-        run: pnpm exec gtm sync --check
-      - name: Validate client repo
-        run: pnpm exec gtm validate
+        run: npx gtm sync --check
+      - name: Validate project repo
+        run: npx gtm validate

package/kit/templates/repo/package.json

@@ -1,8 +1,7 @@
 {
-  "name": "gtm-client-__CLIENT_ID__",
+  "name": "gtm-project-__PROJECT_ID__",
   "private": true,
   "type": "module",
-  "packageManager": "pnpm@10.34.7",
   "scripts": {
     "gtm": "gtm",
     "check": "gtm sync --check && gtm validate"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@veleads/gtm",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "gtm-brain core: process kit (AGENTS.md, skills, templates, schemas) and the gtm CLI for client repos",
   "keywords": [
     "gtm",

package/kit/templates/client/client.yaml

@@ -1,12 +0,0 @@
-# yaml-language-server: $schema=.gtm/schemas/client.schema.json
-version: 1
-client_id: __CLIENT_ID__
-name: __CLIENT_NAME__
-status: onboarding
-started_at: __TODAY__
-owners:
-  gtm_engineer: TODO
-  sdrs: []
-  client_approver: TODO # client-side person who signs off ICP and copy
-regions: [TODO]
-features: {} # opt-in core features (see .gtm/ CHANGELOG / FEATURES)