Add marketing-growth community module

[lpalokan]

Module

• Name: marketing-growth (Marketing Growth Suite)
• Repository: https://github.com/lpalokan/bmad-marketing-growth
• Release pinned: v1.0.3 — to be tagged from main once the cleanup PR merges. approved_sha is left null for the reviewer to pin at approval, per the registry template.
• License: MIT
• Category / Subcategory: marketing-and-growth / content-marketing (see note below)

What it is

A complete AI marketing team for B2B SaaS: 15 agents (6 orchestrators: marketing-orchestrator, content-architect, seo-strategist, social-media-strategist, launch-coordinator, growth-analyst + 9 channel specialists: linkedin, twitter, instagram, youtube, tiktok, discord, reddit, pinterest, email-nurture) and 6 workflow orchestrators (marketing-strategy, content-pipeline, social-campaign, launch-sequence, growth-audit, seo-sprint). 21 skills in total — prompt/markdown only, no executable scripts.

Distinguishing feature: every agent enforces a Source Fidelity rule — no invented metrics, benchmarks, conversion rates, or audience sizes. Numbers must come from the user's input or a cited WebSearch result. Sample copy with numbers is explicitly labeled illustrative. This is the primary differentiation from a generic AI marketing assistant.

Changes since the initial submission (v1.0.2 → v1.0.3)

• Removed the ultimate-seo-geo utility skill (and its 23 Python audit scripts). The suite is now 21 prompt-only skills: 15 agents + 6 workflows.
• Fixed invalid YAML frontmatter in the 6 workflow SKILL.md files (an unquoted description: containing Lead: <name> broke GitHub's frontmatter render).
• Wired up agent capabilities: growth-analyst and the 9 specialist agents now explicitly state how each capability code is fulfilled.
• Version aligned to 1.0.3 across module.yaml, plugin.json, and marketplace.json.

Acceptance checklist (per GOVERNANCE.md / CONTRIBUTING.md)

• Built with BMad Builder, BMad skill structure throughout (SKILL.md + customize.toml per agent; workflow.yaml per workflow)
• Validate Module (VM) equivalent passes — see layout note below (no critical or high findings)
• .claude-plugin/marketplace.json present and valid
• Tagged release v1.0.3 on a public GitHub repo (pending cleanup-PR merge)
• MIT license; original MatthiasMRC/bmad-marketing-growth (Matthias 2025) copyright preserved alongside fork (Lauri Palokangas 2026) copyright in LICENSE
• Valid category + subcategory from categories.yaml
• Module does not override, disable, or circumvent BMad core
• No malicious behavior — the module is now entirely prompt/markdown; there are no scripts, network calls, or obfuscated code
• No duplication of an official module — no official BMad marketing module exists; differentiated by the Source Fidelity guardrail and the multi-channel team structure

Notes for the reviewer

Non-standard layout — repo-root module.yaml. This module's module.yaml lives at the repo root (/module.yaml) rather than inside a *-setup skill or as assets/module.yaml. BMAD's installer supports this via resolveInstalledModuleYaml's 8-path discovery scan, but it's the less-common variant. The module_definition: module.yaml field in the registry entry reflects this. The standard bmad-module-builder validate-module.py doesn't natively handle this layout, so equivalent VM checks were performed manually (file presence, agent roster ↔ customize.toml drift, code/name/icon uniqueness, manifest ↔ filesystem consistency, schema fields, capability registration). All checks pass on v1.0.3.

Cross-cutting subcategory. The suite spans content-marketing, social-media, seo, email-marketing, and analytics. I picked content-marketing as the broadest single label that fits the orchestration + content-architect + workflow layer. If the marketplace convention for cross-cutting suites differs, let me know and I'll re-pin.

Upstream credit. This is a fork of MatthiasMRC/bmad-marketing-growth. The fork removes skills/dwf-tov/, skills/marketing-growth-setup/, and skills/ultimate-seo-geo/, moves the BMAD manifest to the repo root, and adds the Source Fidelity rule to every agent. README and LICENSE credit Matthias prominently.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

[coderabbitai]

Walkthrough

A new registry manifest is added for the "Marketing Growth Suite" community module, populating module identity, descriptive metadata, repository and module references, categorization and keywords, and initial version/approval fields.

Changes

Marketing Growth Module Registry

Layer / File(s)	Summary
Marketing Growth Suite metadata registry/community/marketing-growth.yaml	New registry manifest entry defining module identity, display details, repository linkage, author/license information, categorization, keywords, and version 1.0.3 with approved_tag: v1.0.3, placeholder approval metadata, and trust_tier: unverified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped to the registry, bright and spry,
A new suite listed beneath the sky,
Versioned and tagged with a hopeful cheer,
Marketing Growth now blossoms here — 🎉🌱

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and directly describes the main change: adding a new community module registry entry for the marketing-growth module.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@registry/community/marketing-growth.yaml`:
- Line 25: The approved_sha field in the manifest (approved_sha) is unset while
the PR description and the v1.0.2 tag reference different commit SHAs
(911964c0851b... vs 7a2da646c...), so confirm the correct target commit for the
v1.0.2 release and then update the repo consistently: if the PR SHA
(911964c0851b...) is correct, retag v1.0.2 to point at that commit (and update
the tag in git) and then set approved_sha to that SHA; if the existing tag
(7a2da646c541...) is correct, update the PR description to reference
7a2da646c541... and set approved_sha to that tag's SHA; ensure approved_sha in
registry/community/marketing-growth.yaml matches the final chosen commit SHA.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6bf9adfe-90e0-4523-a98a-668c9d41c449

📥 Commits

Reviewing files that changed from the base of the PR and between ff238fa and d75da27.

📒 Files selected for processing (1)

• registry/community/marketing-growth.yaml

[bmadcode]

@lpalokan it appears there are some errors in some of the source files in the repo - looking at some files present errors when viewing the files in github. also - its a bit hard to tell, but it seems many of the agents list capabilities that do not actual reference another existing skill or prompt - how does this all work?

[lpalokan]

@bmadcode Thanks for giving it a glance. Could it be that they're inherited from the original repository and the author. I'll have a look, and if you have more specific input, that would be great.

I'll also prune the ultimate seo/geo skill from the package as that's contained somewhere else. It was a leftover from my own needs.

[lpalokan]

@bmadcode Thanks again — both points were valid and are now fixed. The fix PR (lpalokan/bmad-marketing-growth#3) is merged and I've re-pinned this submission to a new release, v1.0.3: https://github.com/lpalokan/bmad-marketing-growth/releases/tag/v1.0.3

1. "Errors when viewing files in GitHub"
Root cause was invalid YAML frontmatter in the 6 workflow SKILL.md files (content-pipeline, growth-audit, launch-sequence, marketing-strategy, seo-sprint, social-campaign). Their description: ended with Lead: <name> — unquoted, the embedded : made GitHub's frontmatter parser treat it as a nested mapping, so those files rendered as malformed. Fixed by quoting the description strings. Every .md / .yaml / .json in the repo now parses cleanly.

2. "Agents list capabilities that don't reference a skill or prompt — how does this work?"
Two agent shapes by design:

• 6 orchestrators (marketing-orchestrator, content-architect, seo-strategist, social-media-strategist, launch-coordinator, growth-analyst): the Capabilities table has a Prompt column mapping each code to prompts/<name>.md, and On Activation instructs the agent to read that file on selection. All referenced prompt files exist — cross-checked, zero broken references.
• 9 specialists (linkedin, twitter, instagram, youtube, tiktok, discord, reddit, pinterest, email-nurture): capabilities are fulfilled inline, conversationally — no prompt files by design.

Your read was fair because of two real gaps, now fixed: growth-analyst had its prompt files but was missing the step that reads them, and the 9 specialists never stated that codes are handled inline. Every agent now has an explicit capability-handling step.

Also removed the bundled ultimate-seo-geo utility (it lives elsewhere) — the suite is now 21 prompt-only skills: 15 agents + 6 workflows.

For pinning: v1.0.3 is a lightweight tag, so refs/tags/v1.0.3 resolves directly to the commit (no annotated-tag indirection this time). The commit SHA to set as approved_sha is 9ceb66fe6fdf9e83e899ef68626f7134e99c0c29.