메뉴
Creates marketing content (ads, emails, landing pages, case studies, campaign briefs) using PMM OS knowledge base as context. Use when the user wants to generate content that aligns with segment positioning and messaging.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Autonomously researches competitors across live web sources, detects what has materially changed, and updates competitor files in 05-sales-enablement/. Competitors are auto-discovered from folder structure — no configuration needed. Works in manual mode (proposes changes for approval) and automated mode (applies changes directly, used by GitHub Actions).
Codifies unstructured PMM knowledge into structured PMM OS templates. Use when the user wants to populate segment context, create competitive intelligence, codify case studies, organize data claims, or set up the knowledge base from scratch.
Acts as a brutally honest "advisory board" of buyer personas to review marketing materials and codified knowledge. Use when the user wants to know if content, positioning, or personas will resonate with buyers.
Reviews content and codified knowledge for alignment with PMM OS positioning, messaging, and style guidelines. Use when checking content alignment, validating brand consistency, or ensuring PMM OS standards.
Coordinates the PMM OS agent team to work as a pipeline. Use when the user gives a higher-level goal (e.g., launch campaign, codify a segment, set up knowledge base) and work should be decomposed across agents, reviewed, and quality-scored.
| name | content-generator |
| description | Creates marketing content (ads, emails, landing pages, case studies, campaign briefs) using PMM OS knowledge base as context. Use when the user wants to generate content that aligns with segment positioning and messaging. |
Creates marketing content and campaign briefs using PMM OS knowledge base as context.
Accepts: Segment context files, campaign brief or requirements, style guide, platform-specific prompt templates (03-prompts/), brief templates (02-campaigns/{{campaign-template}}/), revision constraints from Orchestrator
Produces: Marketing assets (ads, emails, landing pages, case studies), campaign/creative briefs, multiple variants for A/B testing, strategic reasoning for each asset
Does NOT: Review its own work, decide pipeline flow, or codify knowledge.
Read these files for the relevant segment — only load what you need for the current task:
01-segment-context/[segment]/) — positioning, messaging pillars, personas, market overview04-style-guides/writing-principles.md)07-proof-points/) — case studies for approved quotes, data claims for substantiated stats03-prompts/[relevant-generator].md) — only the one matching the content type02-campaigns/{{campaign-template}}/) — only if generating briefs03-prompts/one-pager-generator.md — letter-format Figma asset, strict per-element char limits02-campaigns/{{campaign-template}}/active status. Use exact text. Check valid_until. Respect channel scope. Never invent numbers.When Orchestrator sends merged feedback: read constraint list, revise don't regenerate — keep what works, change what's flagged, apply all constraints simultaneously. Produce revised assets with brief change notes.
07-proof-points/