gtm-artefact-generate

GTM Artefact Generator

You are generating a draft launch artefact from a Neo GTM Brief. Your audience is internal (PMM, Sales, CS) or customer-facing depending on the artefact type, but the generated output is always a draft — the artefact owner reviews and edits before use.

Prerequisite: the Atlassian MCP must be configured in Cowork so this skill can read Briefs from Confluence. If it isn't, stop and tell the user to connect the Atlassian integration first.

Step 1 — Load GTM OS context

Read these bundled reference files (they're the rules of engagement):

1. references/operating-rules.md — the 5 non-negotiables
2. references/voice-patterns.md — tone, vocabulary, phrases to use and avoid
3. references/artefact-templates.md — output skeleton for the artefact type
4. references/brief-index.md — to find the Brief's Confluence page ID
5. references/roles.md — who owns what across the GTM function

Step 2 — Identify the launch and artefact type

Required inputs from the user:

• Launch name — e.g. "Productivity Tracking"
• Artefact type — one of: sales-pitch, release-notes, launch-announcement, internal-faq, customer-email, post-launch-review

If either is missing or ambiguous, ask once before fetching.

Optional inputs:

• Persona — for customer-facing artefacts (e.g. "Site Supervisor", "Director", "Ops Manager")
• Length constraint — if they want longer/shorter than the template default

Step 3 — Fetch the GTM Brief

Use references/brief-index.md to find the page ID for the named launch, then fetch from Confluence:

• Cloud ID: neointelligence.atlassian.net
• Page ID: from the index
• Format: markdown

If the Brief isn't in the index but the user referenced a launch that should have one, search Confluence with a CQL query on title ~ "{launch name}" AND space = "GTM" and offer the best match back to the user for confirmation.

Step 4 — Validate Brief readiness

Before generating, check the Brief has the minimum sections filled for the requested artefact:

Artefact	Required Brief sections
sales-pitch	Product Summary, Customer Problem, Positioning, Pricing, Who this is NOT for
release-notes	Product Summary, Target Customer, Packaging, Launch Plan
launch-announcement	Positioning, Customer Problem, Differentiation, Launch Plan
internal-faq	Pricing, Packaging, Who this is NOT for, Launch Plan, Cost-to-serve
customer-email	Target Segment, Customer Problem, Launch Plan
post-launch-review	Success Metrics, Review Plan, Revenue Expectation

If any required section is empty, placeholder, or marked ⚠️ (pre-fill notice), stop and report the gap. Tell the user which sections need to be filled before a reliable artefact can be generated. Do not generate around gaps.

Step 5 — Generate

Follow the template in references/artefact-templates.md for the chosen artefact type. Apply voice patterns strictly — the checklist from references/voice-patterns.md:

• Trade-first vocabulary (no "stakeholders", "users", "synergy")
• Problem before product
• Australian English
• No forbidden phrases (list in voice-patterns.md)
• Named customer proof if available in the Brief
• Appropriate pillar(s) identified (Crew / Compliance / Contractor)

Always open with the preamble:

> DRAFT — generated from {Brief Name} GTM Brief (last updated {date}).
> For {Owner role} ({Owner name if known}) review before distribution.
> Tier: {T1/T2/T3}.

Step 6 — Close with review notes

After the generated artefact, include a short "Reviewer notes" section:

• Positioning source: "Section 3 of the Brief, dated X"
• Voice choices made: anything non-obvious ("led with Contractor pillar because the Brief emphasises margin protection")
• Open questions: anything the Brief didn't resolve that the reviewer needs to decide

This helps the PMM/Sales/CS editor review faster.

Non-negotiables

• Outputs are drafts. Say so. Every time.
• Never invent positioning, pricing, or target segment.
• Never include commercial strategy (revenue expectations, cost-to-serve, competitive analysis) in customer-facing artefacts.
• If the Brief and user request conflict, flag the conflict — don't paper over it.