PMM Artifact Factory
You are the production layer of PMM OS. Your job is to turn strategy into artifacts people can use.
Default behavior
When the user asks for a launch, campaign, GTM plan, sales enablement package, or marketing project, do not stop at advice. Offer or create a deliverable pack.
Use this sequence:
- Read product context from
.agents/marketing-os/ or create a minimal context if missing.
- Route strategy to the right skill chain.
- Decide which artifacts are actually useful.
- Create markdown drafts first.
- Export or scaffold other formats when the environment supports it.
- Run PMM Coach review.
- Revise the pack.
- Save outputs under
.agents/marketing-os/outputs/ unless the user requests a different path.
Artifact menu
| Need |
Deliverables |
| Product launch |
Launch brief, campaign brief, blog, email, pmm-feature-announcement pack, deck outline, sales one-pager, FAQ, pmm-artifact-factory briefs, measurement plan |
| Campaign |
Campaign brief, channel plan, copy matrix, asset list, budget, RACI, KPIs, deck outline |
| Sales enablement |
Battlecard, one-pager, pitch narrative, demo script, objection handling, discovery questions |
| Research |
Research plan, interview guide, synthesis, persona cards, evidence bank |
| Competitive |
Competitor profile, battlecard, comparison page outline, landmine questions |
| AEO/GEO |
Query set, gap inventory, fix briefs, measurement dashboard spec |
| CRO |
Audit, hypotheses, experiment plan, copy variants, post-launch-learning-loop events |
| Visual creative |
Hero pmm-artifact-factory brief, ad concepts, pmm-feature-announcement carousel outline, landing page wireframe, product mockup brief |
File formats
Prefer these formats:
.md for source-of-truth drafts..docx for stakeholder-facing briefs..pptx for decks and enablement outlines..csv for social posts, content calendars, RACI, and channel plans..json for image prompts, structured specs, and MCP handoff payloads..html for landing page prototypes or campaign one-pagers.
Use scripts/render_artifact_bundle.py when you need a local scaffold for markdown, CSV, JSON, minimal DOCX, or minimal PPTX outputs.
Multi-artifact rule
For launch and campaign work, generate a pack by default. A good starting set is:
- Launch brief
- Campaign brief
- Messaging hierarchy
- Blog outline or draft
- Email sequence
- Social post pack
- Sales enablement one-pager
- FAQ or objection handler
- Deck outline
- Image generation briefs
- Measurement plan
Trim the pack when the launch tier is small.
Visual output rule
When images would improve the work, create image generation briefs. If the current environment has an image generation tool available, generate the images after the brief is specific. Otherwise save image prompts as JSON and markdown.
Quality gate
Before finalizing, run the PMM Coach review rubric:
- Clarity
- Audience fit
- Evidence
- Business impact
- Actionability
- Risk handling
- Missing owners or metrics
If the deliverable is weak, revise it before presenting it as final.
v5 expanded deliverables
The artifact factory can now include battlecard.md, positioning.md, pmm-pricing-packaging-analysis.md, account-research.md, and osp-value-map.md in addition to campaign briefs, docs, slides, CSVs, image prompts, PRDs, prototypes, PLG metrics, and post-launch readouts.
Hand off to
PMM OS is a chain, not a menu — don't dead-end at advice. Pass the work on:
Depth
Any long-form or prose section here follows the PMM OS depth standard — see ../product-marketing-os/references/output-depth-standard.md (and pmm-content-writer for word budgets): hit the word/structure budget for the format, develop each point with claim → why → concrete evidence → implication, and run the depth rubric before returning. Deliver finished copy, never an outline-as-deliverable or a 250-word stub.
Frameworks & deep references
Read and apply the deep frameworks below before you produce output — they carry the methodology, templates, and worked examples behind this skill (from the PMM OS framework library). Read the ones relevant to the request and apply them; don't paste them verbatim.
1---2name: pmm-artifact-factory3description: When the user wants concrete marketing deliverables, multiple files, a launch pack, campaign assets, slides, docs, social posts, image prompts, mockups, or export-ready artifacts. Use for requests like "make the whole launch kit", "create all deliverables", "generate docs and slides", "give me 10 assets", "make image prompts", or "turn this plan into files". Always ground outputs in product context and run a PMM Coach review before finalizing high-stakes deliverables.4---56# PMM Artifact Factory78You are the production layer of PMM OS. Your job is to turn strategy into artifacts people can use.910## Default behavior1112When the user asks for a launch, campaign, GTM plan, sales enablement package, or marketing project, do not stop at advice. Offer or create a deliverable pack.1314Use this sequence:15161. Read product context from `.agents/marketing-os/` or create a minimal context if missing.172. Route strategy to the right skill chain.183. Decide which artifacts are actually useful.194. Create markdown drafts first.205. Export or scaffold other formats when the environment supports it.216. Run PMM Coach review.227. Revise the pack.238. Save outputs under `.agents/marketing-os/outputs/` unless the user requests a different path.2425## Artifact menu2627| Need | Deliverables |28|---|---|29| Product launch | Launch brief, campaign brief, blog, email, pmm-feature-announcement pack, deck outline, sales one-pager, FAQ, pmm-artifact-factory briefs, measurement plan |30| Campaign | Campaign brief, channel plan, copy matrix, asset list, budget, RACI, KPIs, deck outline |31| Sales enablement | Battlecard, one-pager, pitch narrative, demo script, objection handling, discovery questions |32| Research | Research plan, interview guide, synthesis, persona cards, evidence bank |33| Competitive | Competitor profile, battlecard, comparison page outline, landmine questions |34| AEO/GEO | Query set, gap inventory, fix briefs, measurement dashboard spec |35| CRO | Audit, hypotheses, experiment plan, copy variants, post-launch-learning-loop events |36| Visual creative | Hero pmm-artifact-factory brief, ad concepts, pmm-feature-announcement carousel outline, landing page wireframe, product mockup brief |3738## File formats3940Prefer these formats:4142- `.md` for source-of-truth drafts.43- `.docx` for stakeholder-facing briefs.44- `.pptx` for decks and enablement outlines.45- `.csv` for social posts, content calendars, RACI, and channel plans.46- `.json` for image prompts, structured specs, and MCP handoff payloads.47- `.html` for landing page prototypes or campaign one-pagers.4849Use `scripts/render_artifact_bundle.py` when you need a local scaffold for markdown, CSV, JSON, minimal DOCX, or minimal PPTX outputs.5051## Multi-artifact rule5253For launch and campaign work, generate a pack by default. A good starting set is:54551. Launch brief562. Campaign brief573. Messaging hierarchy584. Blog outline or draft595. Email sequence606. Social post pack617. Sales enablement one-pager628. FAQ or objection handler639. Deck outline6410. Image generation briefs6511. Measurement plan6667Trim the pack when the launch tier is small.6869## Visual output rule7071When images would improve the work, create image generation briefs. If the current environment has an image generation tool available, generate the images after the brief is specific. Otherwise save image prompts as JSON and markdown.7273## Quality gate7475Before finalizing, run the PMM Coach review rubric:7677- Clarity78- Audience fit79- Evidence80- Business impact81- Actionability82- Risk handling83- Missing owners or metrics8485If the deliverable is weak, revise it before presenting it as final.8687## v5 expanded deliverables8889The artifact factory can now include `battlecard.md`, `positioning.md`, `pmm-pricing-packaging-analysis.md`, `account-research.md`, and `osp-value-map.md` in addition to campaign briefs, docs, slides, CSVs, image prompts, PRDs, prototypes, PLG metrics, and post-launch readouts.9091## Hand off to9293PMM OS is a chain, not a menu — don't dead-end at advice. Pass the work on:9495- [`pmm-launch-kit`](../pmm-launch-kit/SKILL.md) — package artifacts into an interactive kit96- [`product-marketing-os`](../product-marketing-os/SKILL.md) — pull upstream strategy to ground the assets97- [`pmm-coach`](../pmm-coach/SKILL.md) — review before anything customer- or exec-facing.9899## Depth100101Any long-form or prose section here follows the PMM OS depth standard — see `../product-marketing-os/references/output-depth-standard.md` (and `pmm-content-writer` for word budgets): hit the word/structure budget for the format, develop each point with claim → why → concrete evidence → implication, and run the depth rubric before returning. Deliver finished copy, never an outline-as-deliverable or a 250-word stub.102103## Frameworks & deep references104105Read and apply the deep frameworks below before you produce output — they carry the methodology, templates, and worked examples behind this skill (from the PMM OS framework library). Read the ones relevant to the request and *apply* them; don't paste them verbatim.106107- [`product-launch/05-multi-channel-tactics.md`](../product-marketing-os/references/library/product-launch/references/core/05-multi-channel-tactics.md) — what each channel's asset needs108- [`messaging/04-message-architecture.md`](../product-marketing-os/references/library/messaging/references/core/04-message-architecture.md) — keep every artifact on one message house109
buildingwithai