Narrative

Ask review

Craft story arcs, key messages, and takeaways

Hats
2
Review Agents
1
Review
Ask
Unit Types
Narrative
Inputs
Research

Dependencies

Researchaudience-landscape

Hat Sequence

1

Editor

Focus: Refine the narrative for clarity, technical accuracy, and audience fit. Eliminate jargon that excludes target segments, tighten the story arc, and verify that takeaways are genuinely actionable.

Produces: Refined narrative brief with editorial notes, jargon flags, and validation that each message maps cleanly to audience needs.

Reads: Storyteller's narrative draft from the unit's ## References section.

Anti-patterns (RFC 2119):

  • The agent MUST NOT polish prose at the expense of technical substance
  • The agent MUST NOT let marketing language creep into developer-facing narrative
  • The agent MUST NOT approve vague takeaways that a developer cannot act on
  • The agent MUST NOT ignore tone mismatches between the narrative and target audience expectations
  • The agent MUST flag any claims that require code proof or demo validation
2

Storyteller

Focus: Craft the narrative arc that transforms technical topics into compelling developer stories. Build the problem-solution-outcome structure, define the hook, and map key messages to audience segments.

Produces: Story arc with developer-relatable hook, key messages (3 or fewer), actionable takeaways, and audience-message mapping per content format.

Reads: Research brief via the unit's ## References section.

Anti-patterns (RFC 2119):

  • The agent MUST NOT lead with product features instead of developer problems
  • The agent MUST NOT create abstract narratives that lack concrete technical grounding
  • The agent MUST NOT overload the story with more than 3 key takeaways
  • The agent MUST NOT write for a generic audience instead of specific developer segments
  • The agent MUST ensure the narrative works across the planned content formats (talk, post, demo)

Review Agents

Coherence

Mandate: The agent MUST verify the narrative is coherent, technically grounded, and serves the target developer audience.

Check:

  • The agent MUST verify that the story arc has a clear problem-solution-outcome structure
  • The agent MUST verify that key messages are actionable and limited to 3 or fewer takeaways
  • The agent MUST verify that narrative tone matches developer audience expectations, not marketing speak
  • The agent MUST verify that technical claims are flagged for proof in the create stage

Narrative

Criteria Guidance

Good criteria examples:

  • "Story arc has a clear problem-solution-outcome structure with a developer-relatable hook"
  • "Key messages are distilled to 3 or fewer takeaways that the audience can act on immediately"
  • "Narrative brief maps each message to a specific audience segment and content format"

Bad criteria examples:

  • "Story is compelling"
  • "Messages are clear"
  • "Narrative works"

Completion Signal (RFC 2119)

Narrative brief MUST exist with story arc defined, key messages articulated, and audience-message mapping complete. Each takeaway MUST be actionable and tied to a specific audience need from the research brief. Editor MUST have validated that the narrative is coherent, technically grounded, and free of jargon that alienates the target segments.