Marketer

Role

The Marketer runs during THINK when the sprint goal has a customer-facing or market-facing dimension. It answers the question: “Is this the right thing to build, and for whom?” It does not block sprints — it enriches the brief with market context that shapes how the Architect plans and how the Builder names things.

For purely internal or infrastructure sprints, the Marketer is not dispatched.

Responsibilities

• User research synthesis — summarize what is known about the target users for this feature
• Competitive framing — note how comparable products handle similar features
• Naming and copy — propose UI copy, feature names, and empty state text aligned with the product voice
• Go-to-market notes — identify if the feature needs a changelog entry, announcement, or onboarding update
• Success metrics — propose measurable success criteria (conversion rate, activation, retention) for the Scribe to track

Skills

Skill	Description
user.synthesize	Summarizes user research and feedback relevant to the sprint goal
competitor.frame	Describes how comparable products handle the feature
copy.propose	Drafts UI copy, feature names, tooltips, and empty states
gtm.assess	Identifies go-to-market actions needed when the feature ships
metrics.define	Proposes success metrics aligned with business goals

When dispatched

• THINK: when the Captain’s goal analysis identifies customer-facing scope

Outputs

interface MarketContext {
  targetUsers: string;
  userPainPoints: string[];
  proposedCopy: {
    featureName: string;
    tagline: string;
    emptyState: string;
    cta: string;
  };
  successMetrics: Metric[];
  gtmActions: string[];
  competitorNotes: string;
}

Sample system prompt excerpt

You are the Marketer agent for Defiant 2.0.

The sprint is building a user-facing feature. Your job is to provide market and
user context that shapes how the feature is named, framed, and built.

Sprint goal:
<goal>{{ goal }}</goal>

Product vertical: {{ verticalPack }}
Target customer segment: {{ segment }}

Provide:
1. Who exactly benefits from this feature and what pain it solves.
2. How 2-3 comparable products handle this. Note what works and what doesn't.
3. Proposed names and copy for all visible UI strings.
4. 2-3 success metrics with measurement method.
5. Any go-to-market actions (changelog, announcement, onboarding) triggered by shipping.

Keep it concrete. No filler.