@growthub/cli 0.3.54 → 0.3.55

package/assets/worker-kits/growthub-twenty-crm-v1/examples/pipeline-automation-sample.md

@@ -0,0 +1,132 @@
+# Pipeline Automation Brief — Growthub (SAMPLE)
+
+**Date:** 2026-04-15  
+**Kit:** `growthub-twenty-crm-v1`  
+**Mode:** `cloud`
+
+> **Note:** This is a sample output. Adapt all values to the actual client context.
+
+---
+
+## AUTOMATION INVENTORY
+
+| # | Automation name | Trigger | Action | Status |
+|---|---|---|---|---|
+| 1 | Lead Qualified — Assign Rep + Create Follow-Up Task | Stage changes to QUALIFIED | Assign owner, create Task | planned |
+| 2 | Demo Scheduled — Notify Slack | Stage changes to DEMO | Send outbound webhook to Slack | planned |
+| 3 | Closed Won — Create Customer Onboarding Task | Stage changes to CLOSED_WON | Create Task, update field | planned |
+
+---
+
+## AUTOMATION 1 — LEAD QUALIFIED: ASSIGN REP AND CREATE FOLLOW-UP TASK
+
+**Purpose:** When a lead's stage changes to QUALIFIED, assign the opportunity to the next available sales rep (round-robin, two reps) and create a follow-up task due in 24 hours.
+
+### Trigger
+
+| Property | Value |
+|---|---|
+| Trigger type | `on_field_change` |
+| Target object | `Opportunity` |
+| Field | `stage` |
+| Previous value | any (except QUALIFIED) |
+| New value | `QUALIFIED` |
+
+### Action sequence
+
+| Step | Action type | Target | Parameters |
+|---|---|---|---|
+| 1 | `assign_owner` | `Opportunity` | Round-robin between [Sales Rep 1 ID] and [Sales Rep 2 ID] |
+| 2 | `create_task` | `Person` (pointOfContact) | `title: "Follow up with [Person name]", dueAt: +24h, assignee: opportunity.assignee` |
+| 3 | `update_field` | `Opportunity` | `qualifiedAt: now()` (custom date field) |
+
+### Failure behavior
+
+**If step 1 fails (assignment):** Assign to CRM Admin as fallback  
+**If step 2 fails (task creation):** Retry once after 60 seconds; if still failing, send in-app notification to CRM Admin  
+**If step 3 fails (field update):** Log error; non-critical, do not halt
+
+### Monitoring
+
+Check the automation execution log in Twenty > Settings > Workflows weekly. Expected volume: 5–15 triggers per week.
+
+---
+
+## AUTOMATION 2 — DEMO SCHEDULED: NOTIFY SLACK
+
+**Purpose:** When a deal enters the DEMO stage, post a message to the #sales-pipeline Slack channel so the full team sees demo activity in real time.
+
+### Trigger
+
+| Property | Value |
+|---|---|
+| Trigger type | `on_field_change` |
+| Target object | `Opportunity` |
+| Field | `stage` |
+| Previous value | `QUALIFIED` |
+| New value | `DEMO` |
+
+### Action sequence
+
+| Step | Action type | Target | Parameters |
+|---|---|---|---|
+| 1 | `send_webhook` | Slack Incoming Webhook URL | See payload below |
+
+**Slack payload:**
+
+```json
+{
+  "text": "🎯 Demo stage reached: *{{opportunity.name}}* — assigned to {{opportunity.assignee.name}}. Close date: {{opportunity.closeDate}}",
+  "channel": "#sales-pipeline"
+}
+```
+
+### Failure behavior
+
+**If webhook fails:** Retry 3× (5s, 15s, 45s). If all retries fail: log error and send in-app notification to CRM Admin. Non-critical — pipeline is not blocked.
+
+---
+
+## AUTOMATION 3 — CLOSED WON: CREATE ONBOARDING TASK
+
+**Purpose:** When a deal is marked as CLOSED_WON, automatically create a customer onboarding task assigned to the CS Manager.
+
+### Trigger
+
+| Property | Value |
+|---|---|
+| Trigger type | `on_field_change` |
+| Target object | `Opportunity` |
+| Field | `stage` |
+| Previous value | any |
+| New value | `CLOSED_WON` |
+
+### Action sequence
+
+| Step | Action type | Target | Parameters |
+|---|---|---|---|
+| 1 | `create_task` | `Person` (pointOfContact) | `title: "Onboard [Person name] — [Company name]", dueAt: +3 days, assignee: [CS Manager ID]` |
+| 2 | `update_field` | `Opportunity` | `closedAt: now()` (custom date field) |
+| 3 | `send_webhook` | Slack Incoming Webhook | Post to #customer-success: "New customer: [Company name]" |
+
+### Failure behavior
+
+**If task creation fails:** Retry once; then send email notification to CS Manager directly  
+**If Slack webhook fails:** Retry 3×; if all fail, log — non-critical
+
+---
+
+## AUTOMATION DESIGN DECISIONS
+
+| Decision | Choice | Rationale |
+|---|---|---|
+| Assignment method | Round-robin (2 reps) | Equal load distribution; no territory segmentation needed at current team size |
+| Slack notification trigger | Stage change to DEMO (not QUALIFIED) | QUALIFIED happens frequently (5–15/week); only DEMO warrants team visibility |
+| Onboarding task assignee | CS Manager (fixed) | Single CS contact at current team size; revisit when team grows |
+
+---
+
+## OPEN QUESTIONS
+
+- [ ] Should the Closed Won Slack notification include the deal amount? (confirm with head of sales)
+- [ ] What is the round-robin assignment rule when one rep is on leave — assign to the other rep only, or default to CRM Admin?

package/assets/worker-kits/growthub-twenty-crm-v1/growthub-meta/README.md

@@ -0,0 +1,114 @@
+# Growthub Agent Worker Kit — Twenty CRM v1
+
+**Kit ID:** `growthub-twenty-crm-v1`  
+**Version:** `1.0.0`  
+**Type:** `worker`  
+**Execution mode:** `export`
+
+---
+
+## What this kit does
+
+This kit gives an agent a self-contained environment for implementing, configuring, and operating Twenty CRM — the open-source Salesforce/Apollo alternative — as a growth stack foundation.
+
+It packages:
+- agent operating instructions
+- a locked CRM methodology
+- runtime and deployment assumptions
+- API, webhook, and data model reference docs
+- CRM implementation templates (12 templates)
+- example output artifacts (4 complete samples)
+- brand kit system
+- output standards
+- setup scripts for local-fork and cloud modes
+- contributor metadata
+
+The intended operator is a growth engineer, CRM consultant, or AI agent responsible for implementing Twenty CRM for a B2B team and building enrichment pipelines, pipeline automations, and integration handoffs on top of it.
+
+---
+
+## Folder structure
+
+```text
+growthub-twenty-crm-v1/
+├── kit.json
+├── bundles/
+├── workers/
+│   └── twenty-crm-operator/
+│       └── CLAUDE.md
+├── brands/
+│   ├── _template/brand-kit.md
+│   ├── growthub/brand-kit.md
+│   └── NEW-CLIENT.md
+├── setup/
+│   ├── clone-fork.sh
+│   ├── verify-env.mjs
+│   └── check-deps.sh
+├── templates/
+│   ├── crm-setup-brief.md
+│   ├── data-model-design.md
+│   ├── lead-enrichment-pipeline.md
+│   ├── pipeline-automation-brief.md
+│   ├── webhook-integration-spec.md
+│   ├── api-query-plan.md
+│   ├── crm-playbook.md
+│   ├── custom-object-design.md
+│   ├── import-mapping.md
+│   ├── workspace-config-checklist.md
+│   ├── integration-handoff.md
+│   └── enrichment-field-map.md
+├── examples/
+│   ├── crm-setup-sample.md
+│   ├── lead-enrichment-sample.md
+│   ├── pipeline-automation-sample.md
+│   └── crm-playbook-sample.md
+├── docs/
+│   ├── twenty-fork-integration.md
+│   ├── api-and-webhooks.md
+│   └── data-model-layer.md
+├── output/
+│   └── README.md
+├── growthub-meta/
+│   ├── README.md
+│   └── kit-standard.md
+├── skills.md
+├── output-standards.md
+├── runtime-assumptions.md
+├── validation-checklist.md
+├── QUICKSTART.md
+└── .env.example
+```
+
+---
+
+## Activation
+
+1. Export the kit via `growthub kit download growthub-twenty-crm-v1`.
+2. Point the agent working directory at the expanded folder.
+3. The agent reads `workers/twenty-crm-operator/CLAUDE.md`.
+4. `skills.md` provides the working method for every session.
+
+---
+
+## Supported output categories
+
+- CRM setup brief
+- data model design
+- lead enrichment pipeline
+- pipeline automation brief
+- webhook integration spec
+- API query plan
+- custom object design
+- import mapping
+- workspace config checklist
+- integration handoff
+- enrichment field map
+- CRM playbook
+
+---
+
+## Source repository
+
+Twenty CRM: [github.com/twentyhq/twenty](https://github.com/twentyhq/twenty)  
+License: MIT  
+Stack: TypeScript / React / NestJS / PostgreSQL / Redis

package/assets/worker-kits/growthub-twenty-crm-v1/growthub-meta/kit-standard.md

@@ -0,0 +1,61 @@
+# Kit Standard — Twenty CRM v1
+
+This document defines the locked contract for this kit.
+
+---
+
+## Required files contract
+
+Every path in `kit.json -> frozenAssetPaths` must exist in every valid release.
+
+---
+
+## Bundle contract
+
+The bundle manifest must remain aligned with `kit.json`:
+- `bundle.kitId` matches `kit.id`
+- `bundle.workerId` matches `entrypoint.workerId`
+- `requiredFrozenAssets` stays a subset of `frozenAssetPaths`
+
+---
+
+## Agent operating rules
+
+The entrypoint file is the operating law. `skills.md` is the methodology.
+
+Required invariants:
+- strict workflow order (Steps 0–10)
+- environment gate passes before any planning work
+- data model is defined before automation or enrichment pipelines
+- deployment mode is always labeled in every output
+- deduplication key is named in every enrichment or import artifact
+- every automation trigger-action pair has a documented failure path
+- no secrets are stored in any kit file or output artifact
+- outputs are operational artifacts, not ideation-only text
+
+---
+
+## Runtime rules
+
+- no secrets stored in kit files
+- agent-only mode is always a valid fallback — no live CRM required for planning work
+- cloud, self-hosted, and local-fork modes are all first-class
+- outputs are Markdown only
+- field names use Twenty's naming conventions (camelCase for fields, PascalCase for objects)
+- SELECT option values use SCREAMING_SNAKE_CASE
+
+---
+
+## Versioning rules
+
+Additive template/docs changes are minor-version work. Entrypoint path changes, export name changes, or fundamental workflow changes require a major version bump.
+
+---
+
+## Scope rules
+
+This kit is scoped to Twenty CRM implementation planning and operator documentation. It does not:
+- provide a live CRM dashboard
+- write application code (it produces specs and handoffs for developers)
+- manage infrastructure directly
+- store client data in kit files

package/assets/worker-kits/growthub-twenty-crm-v1/kit.json

@@ -0,0 +1,108 @@
+{
+  "schemaVersion": 2,
+  "kit": {
+    "id": "growthub-twenty-crm-v1",
+    "version": "1.0.0",
+    "name": "Growthub Agent Worker Kit — Twenty CRM",
+    "description": "Self-contained local execution environment for Twenty CRM — the open-source Salesforce/Apollo alternative. Produces CRM setup plans, data model designs, lead enrichment pipelines, pipeline automation briefs, webhook integration specs, API query plans, and client-ready CRM playbooks for teams adopting Twenty as their growth stack foundation.",
+    "type": "worker",
+    "visibility": "public-open-source",
+    "sourceRepo": "growthub-local",
+    "family": "studio"
+  },
+  "entrypoint": {
+    "workerId": "twenty-crm-operator",
+    "path": "workers/twenty-crm-operator/CLAUDE.md"
+  },
+  "workerIds": [
+    "twenty-crm-operator"
+  ],
+  "agentContractPath": "workers/twenty-crm-operator/CLAUDE.md",
+  "brandTemplatePath": "brands/_template/brand-kit.md",
+  "publicExampleBrandPaths": [
+    "brands/growthub/brand-kit.md"
+  ],
+  "frozenAssetPaths": [
+    "QUICKSTART.md",
+    ".env.example",
+    "skills.md",
+    "output-standards.md",
+    "runtime-assumptions.md",
+    "validation-checklist.md",
+    "workers/twenty-crm-operator/CLAUDE.md",
+    "brands/_template/brand-kit.md",
+    "brands/growthub/brand-kit.md",
+    "brands/NEW-CLIENT.md",
+    "setup/clone-fork.sh",
+    "setup/verify-env.mjs",
+    "setup/check-deps.sh",
+    "output/README.md",
+    "templates/crm-setup-brief.md",
+    "templates/data-model-design.md",
+    "templates/lead-enrichment-pipeline.md",
+    "templates/pipeline-automation-brief.md",
+    "templates/webhook-integration-spec.md",
+    "templates/api-query-plan.md",
+    "templates/crm-playbook.md",
+    "templates/custom-object-design.md",
+    "templates/import-mapping.md",
+    "templates/workspace-config-checklist.md",
+    "templates/integration-handoff.md",
+    "templates/enrichment-field-map.md",
+    "examples/crm-setup-sample.md",
+    "examples/lead-enrichment-sample.md",
+    "examples/pipeline-automation-sample.md",
+    "examples/crm-playbook-sample.md",
+    "docs/twenty-fork-integration.md",
+    "docs/api-and-webhooks.md",
+    "docs/data-model-layer.md",
+    "growthub-meta/README.md",
+    "growthub-meta/kit-standard.md"
+  ],
+  "setupPaths": {
+    "quickstart": "QUICKSTART.md",
+    "envExample": ".env.example",
+    "setupDir": "setup/",
+    "outputDir": "output/"
+  },
+  "outputStandard": {
+    "type": "working-directory",
+    "description": "Exported folder is intended to be pointed at directly by the agent Working Directory. All outputs are Markdown files written to output/<client-slug>/<project-slug>/.",
+    "requiredPaths": [
+      "QUICKSTART.md",
+      ".env.example",
+      "kit.json",
+      "bundles/growthub-twenty-crm-v1.json",
+      "skills.md",
+      "workers/twenty-crm-operator/CLAUDE.md",
+      "brands/_template/brand-kit.md",
+      "brands/growthub/brand-kit.md",
+      "brands/NEW-CLIENT.md",
+      "setup/clone-fork.sh",
+      "setup/verify-env.mjs",
+      "setup/check-deps.sh",
+      "output/README.md",
+      "templates",
+      "docs",
+      "growthub-meta"
+    ]
+  },
+  "bundles": [
+    {
+      "id": "growthub-twenty-crm-v1",
+      "version": "1.0.0",
+      "path": "bundles/growthub-twenty-crm-v1.json"
+    }
+  ],
+  "executionMode": "export",
+  "activationModes": [
+    "export"
+  ],
+  "compatibility": {
+    "cliMinVersion": "0.3.50"
+  },
+  "provenance": {
+    "sourceRepo": "growthub-local",
+    "frozenAt": "2026-04-15T00:00:00.000Z"
+  }
+}

package/assets/worker-kits/growthub-twenty-crm-v1/output/README.md

@@ -0,0 +1,46 @@
+# Output Directory — Twenty CRM v1
+
+This directory is where the agent writes all client deliverables.
+
+---
+
+## Structure
+
+```text
+output/
+└── <client-slug>/
+    └── <project-slug>/
+        ├── <ClientSlug>_CRMSetupBrief_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_DataModelDesign_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_LeadEnrichmentPipeline_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_PipelineAutomationBrief_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_WebhookIntegrationSpec_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_APIQueryPlan_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_CustomObjectDesign_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_ImportMapping_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_WorkspaceConfigChecklist_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_IntegrationHandoff_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_EnrichmentFieldMap_v<N>_<YYYYMMDD>.md
+        └── <ClientSlug>_CRMPlaybook_v<N>_<YYYYMMDD>.md
+```
+
+---
+
+## File naming
+
+Pattern: `<ClientSlug>_<OutputType>_v<N>_<YYYYMMDD>.md`
+
+- `ClientSlug` is PascalCase (e.g. `AcmeCorp`, `Growthub`)
+- `OutputType` matches the artifact type exactly (e.g. `CRMSetupBrief`, `DataModelDesign`)
+- `v<N>` is the version number (start at `v1`, increment on revision)
+- `YYYYMMDD` is the date of production
+
+---
+
+## Rules
+
+- never overwrite an existing version file — create a new version
+- keep one artifact per file
+- Markdown only
+- no placeholder text in any delivered file
+- brand kit DELIVERABLES LOG must be updated after each delivery

package/assets/worker-kits/growthub-twenty-crm-v1/output-standards.md

@@ -0,0 +1,175 @@
+# Output Standards — Twenty CRM v1
+
+This document defines the output contract for every artifact produced by this kit.
+
+---
+
+## OUTPUT FOLDER STRUCTURE
+
+```text
+output/
+└── <client-slug>/
+    └── <project-slug>/
+        ├── <ClientSlug>_CRMSetupBrief_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_DataModelDesign_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_LeadEnrichmentPipeline_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_PipelineAutomationBrief_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_WebhookIntegrationSpec_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_APIQueryPlan_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_CustomObjectDesign_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_ImportMapping_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_WorkspaceConfigChecklist_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_IntegrationHandoff_v<N>_<YYYYMMDD>.md
+        ├── <ClientSlug>_EnrichmentFieldMap_v<N>_<YYYYMMDD>.md
+        └── <ClientSlug>_CRMPlaybook_v<N>_<YYYYMMDD>.md
+```
+
+---
+
+## REQUIRED OUTPUT TYPES
+
+Every full CRM implementation package must include:
+- CRM setup brief
+- data model design
+- lead enrichment pipeline
+- pipeline automation brief
+- webhook integration spec
+- API query plan
+- workspace config checklist
+- integration handoff
+- CRM playbook
+
+Custom object design and import mapping are included when the scope requires them.
+
+---
+
+## REQUIRED SECTIONS
+
+### CRM setup brief
+1. Client context and CRM objective
+2. Deployment mode (cloud / self-hosted / local-fork)
+3. Team size and user roles
+4. Data sources and volume estimates
+5. Integration scope
+6. Go-live timeline and milestones
+7. Success criteria
+
+### Data model design
+1. Standard objects in use and configuration notes
+2. Custom objects (if any) with full field definitions
+3. Relationship map (which objects link to which)
+4. Field type table per object
+5. Display configuration (labels, icons, default views)
+6. Open questions / decisions required
+
+### Lead enrichment pipeline
+1. Enrichment provider(s) and auth mechanism
+2. Source fields provided
+3. Target Twenty fields
+4. Deduplication strategy and match key
+5. Insert vs. merge behavior
+6. Update frequency
+7. Error and failure handling
+
+### Pipeline automation brief
+1. Pipeline name and purpose
+2. Trigger type and object
+3. Trigger conditions (field, value, timing)
+4. Action sequence
+5. Failure / timeout behavior
+6. Monitoring and alerting plan
+
+### Webhook integration spec
+1. Inbound vs. outbound classification
+2. Event name and trigger object
+3. Payload schema
+4. Target endpoint or source
+5. Auth mechanism
+6. Retry policy
+7. Test procedure
+
+### API query plan
+1. Query type (GraphQL / REST)
+2. Object(s) targeted
+3. Filter conditions
+4. Field selection
+5. Expected response structure
+6. Use case and consumer
+
+### Custom object design
+1. Object name and purpose
+2. Field table (name, type, required, options)
+3. Relationship definitions
+4. Creation method (UI vs. metadata API)
+5. Default view configuration
+6. Validation rules
+
+### Import mapping
+1. Source CRM / export format
+2. Column-by-column mapping table
+3. Transformation rules
+4. Deduplication key
+5. Import mode (insert / merge)
+6. Post-import validation steps
+
+### Workspace config checklist
+1. Settings to configure (auth, members, roles, branding)
+2. Integrations to enable
+3. Objects to activate or create
+4. Views and filters to configure
+5. Email and notification settings
+6. API token generation and distribution
+
+### Integration handoff
+1. System integration diagram
+2. Auth credentials required (types only — no values)
+3. Endpoint contracts
+4. Sequence diagram for data flow
+5. Environment checklist (dev / staging / prod)
+6. Rollback plan
+
+### Enrichment field map
+1. Provider name
+2. Provider field → Twenty field table with types and transformations
+3. Deduplication key
+4. Update frequency
+5. Notes and edge cases
+
+### CRM playbook
+1. Team roles and permissions
+2. Daily workflow (record creation, updates, activities)
+3. Pipeline management procedures
+4. Enrichment cadence
+5. Reporting and dashboard instructions
+6. Escalation and handoff protocols
+7. Maintenance and data hygiene checklist
+
+---
+
+## FILE NAMING RULES
+
+Pattern:
+
+```text
+<ClientSlug>_<OutputType>_v<N>_<YYYYMMDD>.md
+```
+
+Rules:
+- `ClientSlug` is PascalCase
+- never overwrite an existing version
+- keep one artifact per file
+- Markdown only
+
+---
+
+## QUALITY BAR
+
+An output is complete when:
+- no placeholder text remains
+- all object and field names match Twenty's naming conventions
+- deduplication keys are named in every enrichment or import artifact
+- every automation trigger-action pair has a documented failure path
+- webhook specs include full payload schemas
+- GraphQL queries are syntactically correct
+- the CRM playbook is written at a level a non-technical team member can execute
+- integration handoff provides enough detail for a developer to implement without asking follow-up questions