@growthub/cli 0.14.5 → 0.14.6

package/assets/worker-kits/growthub-marketing-skills-v1/docs/fork-integration.md

@@ -1,43 +0,0 @@
-# Fork Integration — marketingskills
-
-## Upstream Repository
-
-- **Source**: [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills)
-- **License**: MIT
-- **Stars**: 21k+
-- **Skills**: 40+ marketing skill definitions
-
-## Relationship to This Kit
-
-This worker kit wraps the marketingskills library's frameworks and evaluation methodologies into a Growthub operator kit. The upstream library is a **reference**, not a runtime dependency.
-
-### What we took from the upstream:
-- Marketing domain taxonomy (CRO, SEO, Content, Email, Growth, etc.)
-- Evaluation frameworks (7-dimension CRO, E-E-A-T SEO, sequence architecture)
-- Cross-skill chaining patterns (which skills reference which)
-- Product-marketing-context as the foundational grounding document
-
-### What we added:
-- **Product-marketing context as brand kit** — the upstream's context file becomes our brand kit template with 12 structured sections
-- **Frozen deliverable templates** — structured output templates for each domain
-- **Operator workflow** — 7-step strict-order workflow with mandatory gates
-- **Output standards** — file naming, versioning, quality checklist
-- **Growthub examples** — reference deliverables using Growthub's own product context
-- **Kit packaging** — schemaVersion 2 manifest, bundle, activation modes
-
-### What we intentionally left out:
-- **Individual skill files** — skills are one dimension of the environment, not the centerpiece. The operator's skills.md consolidates all 40+ skills into a dispatch table and framework summaries. Users who want the full individual skill files can install them from the upstream repo alongside this kit.
-- **Tool integrations** — the upstream includes tool-specific integrations (GA4, Stripe, Mailchimp MCP). These are optional and not frozen into this kit. Users add them via their agent's tool configuration.
-- **Installation scripts** — the upstream's `npx skills add` flow is for standalone skill installation. This kit uses the Growthub kit export flow instead.
-
-## Updating from Upstream
-
-When the upstream library releases new skills or framework updates:
-
-1. Review the upstream changelog
-2. Update `skills.md` dispatch table if new skills are added
-3. Update framework summaries if evaluation criteria change
-4. Add new templates if new domains are introduced
-5. Bump the kit version in `kit.json`
-
-The upstream library evolves independently. This kit freezes a specific set of frameworks at a point in time. Not every upstream change needs to be pulled in.

package/assets/worker-kits/growthub-marketing-skills-v1/docs/skill-dispatch-methodology.md

@@ -1,50 +0,0 @@
-# Skill Dispatch Methodology
-
-## How the Operator Routes User Intent
-
-The marketing operator uses a two-phase routing system:
-
-### Phase 1 — Domain Detection
-
-The operator scans the user's request for trigger signals and maps to a primary marketing domain:
-
-| Signal Pattern | Domain |
-|---|---|
-| "conversions", "landing page", "bounce rate", "CRO", URL shared | CRO |
-| "rankings", "traffic", "SEO", "organic", "indexing" | SEO |
-| "content strategy", "blog", "editorial", "pillars" | Content |
-| "email", "sequence", "nurture", "cold outbound" | Email |
-| "launch", "go-to-market", "GTM", "product launch" | Launch |
-| "competitors", "alternatives", "positioning" | Competitive |
-| "write copy", "headline", "ad copy" | Copy |
-| "growth ideas", "referral", "pricing", "churn" | Growth |
-
-When signals are ambiguous or span multiple domains, the 3-question gate resolves the primary domain.
-
-### Phase 2 — Framework Selection
-
-Once the domain is identified, the operator loads the appropriate template and framework from `templates/`. Each framework defines:
-
-1. **Evaluation dimensions** — what to assess
-2. **Scoring criteria** — how to rate findings (where applicable)
-3. **Output structure** — required sections in the deliverable
-4. **Cross-references** — when to chain to another domain
-
-## Cross-Domain Chaining
-
-Skills are interconnected. The operator follows upstream-to-downstream ordering:
-
-```
-customer-research → content-strategy → copywriting
-competitor-analysis → pricing-strategy → launch-strategy
-seo-audit → content-strategy → programmatic-seo
-page-cro → copywriting → ab-test-setup
-```
-
-Each domain in the chain produces its own deliverable. Outputs are never merged across domains.
-
-## Relationship to Upstream Skills
-
-The dispatch table maps to 36+ skills from [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills). The operator consolidates these into 8 primary domains with framework summaries rather than loading individual skill files. This keeps the cognitive load manageable while preserving the evaluation rigor of the underlying frameworks.
-
-Users who want deeper skill-level granularity can install the upstream skills alongside this kit. The operator's dispatch table documents which upstream skill maps to which domain.

package/assets/worker-kits/growthub-marketing-skills-v1/examples/email-sequence-sample.md

@@ -1,75 +0,0 @@
-# Email Sequence Plan — Growthub / Welcome Sequence
-
-**Date:** 2026-04-15
-**Version:** v1
-**Domain:** Email
-**Operator:** marketing-operator
-
----
-
-## Executive Summary
-
-- 5-email welcome sequence over 10 days focused on activation (first kit download)
-- Anchored on the "Growth System" content pillar
-- Emotional arc: Curious → Informed → Equipped → Activated → Connected
-- Primary CTA: Download first worker kit via CLI
-
----
-
-## Sequence Overview
-
-| Field | Value |
-|---|---|
-| Sequence type | Welcome |
-| Email count | 5 |
-| Duration | 10 days |
-| Entry trigger | CLI install (`npx @growthub/create-growthub-local`) |
-| Primary CTA | Download first worker kit |
-| Audience segment | New CLI installers |
-
----
-
-## Emotional Arc
-
-```
-Email 1: Curious → Email 2: Informed → Email 3: Equipped → Email 4: Activated → Email 5: Connected
-```
-
----
-
-## Sequence Map
-
-| Email | Send Day | Subject Theme | Body Arc | CTA | Purpose |
-|---|---|---|---|---|---|
-| 1 | Day 0 | Welcome + what you just installed | Orient — show what's inside the discovery hub | Explore discovery hub | Reduce confusion, build confidence |
-| 2 | Day 2 | Your first worker kit | Educate — explain what kits are and why they matter | Download creative-strategist-v1 | First kit activation |
-| 3 | Day 4 | How to set up product context | Equip — walk through brand kit setup | Create product-marketing-context.md | Enable personalized output |
-| 4 | Day 7 | See what others built | Prove — show real examples and community use cases | Try a second kit | Deepen engagement |
-| 5 | Day 10 | You're part of something | Connect — community, contributing, what's next | Join GitHub / contribute | Build retention loop |
-
----
-
-## Subject Line Matrix
-
-### Email 1 — Welcome
-
-| Variant | Type | Subject Line | Preview Text |
-|---|---|---|---|
-| A | Direct | You just installed Growthub — here's what to do first | Your discovery hub is ready to explore |
-| B | Curiosity | There are 4 kits waiting for you | Each one is a complete marketing environment |
-| C | Personal | Welcome to local-first marketing | Your data stays on your machine — here's how it works |
-| D | Social proof | Join 500+ builders using Growthub kits | Open source, MIT licensed, ready to ship |
-| E | Urgency | Don't skip this — your first 5 minutes matter | Quick setup guide inside |
-
-**Recommended A/B test**: Variant A vs Variant B
-
----
-
-## Platform Notes
-
-| Field | Value |
-|---|---|
-| Email platform | TBD |
-| Segment/tag | new-cli-install |
-| Automation trigger | CLI install event |
-| Unsubscribe handling | Standard CAN-SPAM footer |

package/assets/worker-kits/growthub-marketing-skills-v1/examples/landing-page-cro-sample.md

@@ -1,128 +0,0 @@
-# CRO Audit Brief — Growthub / Homepage
-
-**Date:** 2026-04-15
-**Version:** v1
-**Domain:** CRO
-**Operator:** marketing-operator
-
----
-
-## Executive Summary
-
-- Homepage value proposition is clear but buried below the fold — headline focuses on category rather than benefit
-- CTA copy is generic ("Get Started") and misses the primary conversion action (CLI install)
-- Strong trust signals (open source, MIT license, npm published) but not positioned near the CTA
-- No objection handling before the primary conversion point
-- Quick win: rewrite headline to lead with the benefit, move trust signals above the fold
-
----
-
-## Page Under Review
-
-| Field | Value |
-|---|---|
-| URL | growthub.ai |
-| Page type | Homepage |
-| Traffic source | Organic + GitHub referral |
-| Current conversion rate | Unknown |
-| Primary conversion goal | CLI install via `npx @growthub/create-growthub-local` |
-
----
-
-## 7-Dimension Analysis
-
-### 1. Value Proposition Clarity
-
-**Score:** Adequate (2)
-
-**Findings:** The one-liner "Local-first AI agent runtime" is technically accurate but doesn't communicate the benefit to the user. Visitors from non-technical backgrounds may not understand what "runtime" means in this context.
-
-**Recommendations:** Lead with the outcome: "Ship marketing without hiring an agency" or "Run AI agent kits locally — your data stays on your machine."
-
-### 2. Headline Effectiveness
-
-**Score:** Weak (1)
-
-**Findings:** Headline describes the category (AI agent runtime) rather than the promise. Doesn't match the messaging from GitHub (where most traffic originates) which emphasizes "worker kits" and "local execution."
-
-**Recommendations:** Test benefit-driven headlines that match the traffic source messaging. Options:
-1. "Download a marketing team in one command"
-2. "AI agent kits that actually know your product"
-3. "Local-first worker kits for marketing and growth"
-
-### 3. CTA Placement & Copy
-
-**Score:** Adequate (2)
-
-**Findings:** Primary CTA exists above the fold but uses generic "Get Started" copy. The actual conversion action (CLI install command) is a better CTA since it's one command and feels low-commitment.
-
-**Recommendations:** Replace "Get Started" with the actual install command: `npx @growthub/create-growthub-local` — developers respond better to concrete commands than vague buttons.
-
-### 4. Visual Hierarchy
-
-**Score:** Strong (3)
-
-**Findings:** Clean layout with clear sections. Good use of whitespace. Discovery hub screenshot provides social proof of the actual product experience.
-
-**Recommendations:** No critical changes needed. Consider adding kit-specific screenshots below the fold to show what users actually get.
-
-### 5. Trust Signals
-
-**Score:** Adequate (2)
-
-**Findings:** Open source badge, MIT license mention, and npm published status are present but positioned in the footer area. GitHub stars count is not prominently displayed.
-
-**Recommendations:** Move "MIT Licensed | Open Source | Works with Claude, Cursor, Codex, Gemini" above the fold, near the CTA. Add GitHub stars badge.
-
-### 6. Objection Handling
-
-**Score:** Missing (0)
-
-**Findings:** No objection handling before the CTA. Common objections ("How is this different from ChatGPT?", "Does it work with my agent?", "Is it hard to set up?") are not addressed.
-
-**Recommendations:** Add a 3-row objection-handling section between the hero and the CTA. Use the customer language from the product-marketing context.
-
-### 7. Friction Points
-
-**Score:** Strong (3)
-
-**Findings:** Install is one command. No signup form, no email gate, no account required. This is the lowest-friction conversion path possible for a developer tool.
-
-**Recommendations:** Preserve this simplicity. Do not add a signup wall before the CLI install.
-
----
-
-## Composite Score
-
-| Dimension | Score |
-|---|---|
-| Value Proposition Clarity | 2/3 |
-| Headline Effectiveness | 1/3 |
-| CTA Placement & Copy | 2/3 |
-| Visual Hierarchy | 3/3 |
-| Trust Signals | 2/3 |
-| Objection Handling | 0/3 |
-| Friction Points | 3/3 |
-| **Total** | **13/21** |
-
----
-
-## Quick Wins
-
-1. Rewrite headline to lead with benefit, not category
-2. Replace "Get Started" CTA with the actual install command
-3. Move open-source trust signals above the fold
-
-## High-Impact Changes
-
-1. Add objection-handling section (3 common objections with one-line answers)
-2. Add kit-specific screenshots showing what users actually get after install
-3. Add GitHub stars badge as social proof
-
-## A/B Test Hypotheses
-
-| Test | Hypothesis | Expected Impact | Priority |
-|---|---|---|---|
-| Headline: benefit vs. category | Benefit-driven headline will increase CLI installs by 15-25% | High | 1 |
-| CTA: "Get Started" vs. install command | Showing the actual command will increase clicks by 10-20% | Medium | 2 |
-| Trust signals above fold | Moving trust signals up will reduce bounce rate by 5-10% | Medium | 3 |

package/assets/worker-kits/growthub-marketing-skills-v1/examples/seo-audit-sample.md

@@ -1,102 +0,0 @@
-# SEO Audit Report — Growthub / growthub.ai
-
-**Date:** 2026-04-15
-**Version:** v1
-**Domain:** SEO
-**Operator:** marketing-operator
-
----
-
-## Executive Summary
-
-- Site is indexed and crawlable with clean URL structure
-- Missing XML sitemap limits crawl efficiency for new content
-- Title tags are functional but not keyword-optimized for primary search terms
-- Content depth is thin on key landing pages — competitor pages have 2-3x word count
-- No structured data (JSON-LD) present — missing opportunities for rich results
-
----
-
-## Audit Scope
-
-| Field | Value |
-|---|---|
-| Domain | growthub.ai |
-| Pages audited | Homepage + key landing pages |
-| Tools used | Manual analysis |
-| Priority keywords | "AI agent kits", "local AI tools", "marketing AI agent", "worker kits CLI" |
-
----
-
-## Technical SEO
-
-### Crawlability & Indexation
-
-| Check | Status | Notes |
-|---|---|---|
-| robots.txt | Present | Standard configuration, no unusual blocks |
-| XML sitemap | Missing | No sitemap.xml found — should be added |
-| Canonical tags | Present | Self-referencing canonicals on key pages |
-| Index status | Indexed | Primary pages in Google index |
-| Crawl budget | No concern | Small site, no crawl budget issues |
-
-### Site Speed (Core Web Vitals)
-
-| Metric | Target | Measured | Status |
-|---|---|---|---|
-| LCP | <2.5s | ~1.8s | Pass |
-| INP | <200ms | <100ms | Pass |
-| CLS | <0.1 | <0.05 | Pass |
-
-### Mobile & Security
-
-| Check | Status | Notes |
-|---|---|---|
-| Mobile responsive | Pass | Clean responsive layout |
-| HTTPS | Pass | Valid certificate |
-| Mixed content | None | All resources served over HTTPS |
-
----
-
-## On-Page SEO
-
-### Title Tags
-Homepage title is descriptive but not keyword-optimized. Consider: "Growthub — Local AI Agent Kits for Marketing & Growth | Open Source CLI"
-
-### Heading Structure
-Single H1 on homepage. Logical H2/H3 hierarchy. Good structure.
-
-### Content Optimization
-Key landing pages have 300-500 words. Competitor comparison pages typically have 1,500-2,500 words. Thin content may limit ranking potential for competitive terms.
-
-### Internal Linking
-Basic navigation links present. No contextual internal links between content pages. Adding topic-relevant internal links would improve crawl paths and topical authority.
-
----
-
-## Findings by Priority
-
-### Critical
-
-1. **Finding**: No XML sitemap — **Impact**: New content may not be discovered efficiently — **Fix**: Generate and submit sitemap.xml to GSC
-
-### High
-
-1. **Finding**: No structured data — **Impact**: Missing rich results (FAQ, How-to, Software Application schema) — **Fix**: Add JSON-LD for Software Application, FAQ, and Organization schemas
-2. **Finding**: Thin content on landing pages — **Impact**: Lower ranking potential for competitive terms — **Fix**: Expand key pages to 1,500+ words with depth on use cases
-
-### Medium
-
-1. **Finding**: Title tags not keyword-optimized — **Impact**: Missing ranking signals for primary terms — **Fix**: Rewrite titles to include primary keywords naturally
-
----
-
-## Prioritized Action Plan
-
-| Priority | Action | Effort | Expected Impact |
-|---|---|---|---|
-| 1 | Add XML sitemap and submit to GSC | Low | Improved crawl efficiency |
-| 2 | Add JSON-LD structured data | Medium | Rich results eligibility |
-| 3 | Expand landing page content depth | High | Improved ranking for competitive terms |
-| 4 | Optimize title tags for primary keywords | Low | Incremental ranking improvement |
-| 5 | Add contextual internal links | Low | Better topical authority signals |

package/assets/worker-kits/growthub-marketing-skills-v1/growthub-meta/README.md

@@ -1,5 +0,0 @@
-# Growthub Meta
-
-This directory contains kit packaging metadata for the Growthub worker kit system.
-
-- `kit-standard.md` — Kit packaging standard this kit follows

package/assets/worker-kits/growthub-marketing-skills-v1/growthub-meta/kit-standard.md

@@ -1,25 +0,0 @@
-# Kit Standard — growthub-marketing-skills-v1
-
-## Schema Version
-
-This kit follows `schemaVersion: 2` of the Growthub Worker Kit contract.
-
-## Kit Family
-
-`operator` — Domain-specific operator for marketing workflows.
-
-## Execution Mode
-
-`export` — Kit is exported to a local directory and pointed at by the agent's Working Directory.
-
-## Upstream Source
-
-This kit wraps frameworks from [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills) (MIT license). The upstream library provides the skill definitions and evaluation frameworks. This kit packages them into a Growthub operator environment with brand context, templates, and output standards.
-
-## Activation
-
-```bash
-growthub kit download marketing-skills
-```
-
-Then point your AI agent's Working Directory at the exported folder.

package/assets/worker-kits/growthub-marketing-skills-v1/helpers/README.md

@@ -1,29 +0,0 @@
-# `helpers/` — safe shell tool layer (primitive #6)
-
-A **helper** is a small, deterministic script an agent invokes via one shell call instead of reconstructing a raw pipeline inline. Helpers are reviewable, deterministic, and safer than raw commands.
-
-## Convention
-
-```
-helpers/
-├── README.md                 # this file
-├── <verb>.sh                 # single-purpose shell scripts
-├── <verb>.mjs                # optional: Node-based helper
-└── <verb>.py                 # optional: Python-based helper
-```
-
-Every helper:
-
-1. Carries a one-line header comment: what it does + how to invoke it.
-2. Uses `set -euo pipefail` (or equivalent) — no silent failures.
-3. Has a matching row in the parent `SKILL.md`'s `helpers[]` frontmatter.
-4. Is referenced from `skills.md` at the step the agent should invoke it (no duplicated shell bodies).
-
-## When to promote an inline snippet
-
-- Appears more than once in `skills.md`.
-- Has fragile quoting or path interpolation.
-- Calls a side-effecting binary (ffmpeg, git, gh, npm install).
-- Multiple sub-skills invoke it.
-
-See the parent `SKILL.md` `helpers[]` array for the current roster.

package/assets/worker-kits/growthub-marketing-skills-v1/kit.json

@@ -1,108 +0,0 @@
-{
-  "schemaVersion": 2,
-  "kit": {
-    "id": "growthub-marketing-skills-v1",
-    "version": "1.0.0",
-    "name": "Growthub Agent Worker Kit \u2014 Marketing Operator",
-    "description": "Self-contained marketing execution environment wrapping the open-source marketingskills library (coreyhaines31/marketingskills). Provides structured marketing workflows for CRO, SEO, content strategy, email sequences, paid ads, and growth \u2014 grounded in product-marketing context and brand voice. Skills are one dimension of the kit; the operator workflow, brand kit, templates, and output standards form the complete environment.",
-    "type": "worker",
-    "visibility": "public-open-source",
-    "sourceRepo": "growthub-local",
-    "family": "operator"
-  },
-  "entrypoint": {
-    "workerId": "marketing-operator",
-    "path": "workers/marketing-operator/CLAUDE.md"
-  },
-  "workerIds": [
-    "marketing-operator"
-  ],
-  "agentContractPath": "workers/marketing-operator/CLAUDE.md",
-  "brandTemplatePath": "brands/_template/product-marketing-context.md",
-  "publicExampleBrandPaths": [
-    "brands/growthub/product-marketing-context.md"
-  ],
-  "frozenAssetPaths": [
-    "QUICKSTART.md",
-    ".env.example",
-    "skills.md",
-    "output-standards.md",
-    "runtime-assumptions.md",
-    "workers/marketing-operator/CLAUDE.md",
-    "brands/_template/product-marketing-context.md",
-    "brands/growthub/product-marketing-context.md",
-    "templates/cro-audit-brief.md",
-    "templates/seo-audit-report.md",
-    "templates/content-strategy-plan.md",
-    "templates/email-sequence-plan.md",
-    "templates/launch-checklist.md",
-    "templates/competitor-analysis.md",
-    "examples/landing-page-cro-sample.md",
-    "examples/seo-audit-sample.md",
-    "examples/email-sequence-sample.md",
-    "docs/fork-integration.md",
-    "docs/skill-dispatch-methodology.md",
-    "docs/evaluation-frameworks.md",
-    "setup/verify-env.mjs",
-    "output/README.md",
-    "growthub-meta/README.md",
-    "growthub-meta/kit-standard.md",
-    "SKILL.md",
-    "templates/project.md",
-    "templates/self-eval.md",
-    "helpers/README.md",
-    "skills/README.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-marketing-skills-v1.json",
-      "skills.md",
-      "workers/marketing-operator/CLAUDE.md",
-      "brands/_template/product-marketing-context.md",
-      "brands/growthub/product-marketing-context.md",
-      "templates",
-      "docs",
-      "growthub-meta",
-      "SKILL.md",
-      "templates/project.md",
-      "templates/self-eval.md",
-      "helpers",
-      "helpers/README.md",
-      "skills",
-      "skills/README.md"
-    ]
-  },
-  "bundles": [
-    {
-      "id": "growthub-marketing-skills-v1",
-      "version": "1.0.0",
-      "path": "bundles/growthub-marketing-skills-v1.json"
-    }
-  ],
-  "executionMode": "export",
-  "activationModes": [
-    "export"
-  ],
-  "compatibility": {
-    "cliMinVersion": "0.3.53"
-  },
-  "provenance": {
-    "sourceRepo": "growthub-local",
-    "upstream": "https://github.com/coreyhaines31/marketingskills",
-    "frozenAt": "2026-04-15T00:00:00.000Z"
-  },
-  "workspaceVisibility": "addon",
-  "workspaceCompatible": true,
-  "workspaceCategory": "marketing-operator"
-}

package/assets/worker-kits/growthub-marketing-skills-v1/output/README.md

@@ -1,32 +0,0 @@
-# Output Directory
-
-All operator deliverables are saved here, organized by client and project.
-
-## Structure
-
-```
-output/
-  <client-slug>/
-    <project-slug>/
-      <ClientSlug>_<Domain>_<Type>_v<N>_<YYYYMMDD>.md
-```
-
-## Examples
-
-```
-output/
-  acme/
-    homepage-redesign/
-      Acme_CRO_AuditBrief_v1_20260415.md
-    q2-content/
-      Acme_Content_StrategyPlan_v1_20260415.md
-  growthub/
-    welcome-flow/
-      Growthub_Email_SequencePlan_v1_20260415.md
-```
-
-## Rules
-
-- Never overwrite existing files — increment version (`v1` → `v2`)
-- Always update the deliverables log in the client's product-marketing-context.md
-- Use the exact naming convention — no variations

package/assets/worker-kits/growthub-marketing-skills-v1/output-standards.md

@@ -1,51 +0,0 @@
-# Marketing Operator — Output Standards
-
-All operator outputs must follow these standards.
-
----
-
-## File Naming
-
-```
-output/<client-slug>/<project-slug>/
-  +-- <ClientSlug>_<Domain>_<Type>_v<N>_<YYYYMMDD>.md
-```
-
-Examples:
-- `output/acme/homepage-redesign/Acme_CRO_AuditBrief_v1_20260415.md`
-- `output/acme/q2-content/Acme_Content_StrategyPlan_v1_20260415.md`
-- `output/acme/welcome-flow/Acme_Email_SequencePlan_v1_20260415.md`
-
----
-
-## Required Sections (all deliverables)
-
-1. **Header block** — Client, domain, date, version, operator
-2. **Executive summary** — 3-5 bullet points of key findings or decisions
-3. **Analysis body** — Structured by the domain framework's dimensions
-4. **Prioritized action plan** — Critical → Quick Wins → Long-term
-5. **Next steps** — Clear owner suggestions and timeline
-
----
-
-## Versioning
-
-Never overwrite existing files. Increment the version number:
-- `v1` → `v2` → `v3`
-
-Previous versions are preserved for comparison.
-
----
-
-## Quality Checklist
-
-Before delivering any output, verify:
-
-- [ ] Product-marketing context was loaded and referenced
-- [ ] All framework dimensions were evaluated (none skipped)
-- [ ] Every finding has a specific, actionable recommendation
-- [ ] Recommendations are prioritized (not an unranked list)
-- [ ] Customer language is used over marketing jargon
-- [ ] No fabricated metrics or social proof
-- [ ] File naming convention followed
-- [ ] Deliverables log in brand kit updated