Create

Ask review

Produce the content — posts, slides, demos, videos

Hats
2
Review Agents
2
Review
Ask
Unit Types
Blog Post, Talk, Demo, Video
Inputs
Narrative

Dependencies

Narrativestory-arc

Hat Sequence

1

Content Creator

Focus: Produce the developer content — blog posts, talk slides, video scripts — that executes the narrative arc. Prioritize technical substance and developer utility over production polish.

Produces: Content assets for all planned formats, each following the narrative arc with working code examples, clear structure, and actionable takeaways.

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

Anti-patterns (RFC 2119):

  • The agent MUST NOT write code examples that cannot compile or run
  • The agent MUST NOT create slides with walls of text instead of visual storytelling
  • The agent MUST NOT deviate from the narrative arc without justification
  • The agent MUST NOT produce content that reads as marketing material rather than technical education
  • The agent MUST NOT leave placeholder code or TODO sections in finished assets
2

Demo Builder

Focus: Build working demos and code examples that prove the narrative's technical claims. Ensure demos are reproducible, well-documented, and suitable for live presentation or self-guided exploration.

Produces: Working demo projects with README, setup instructions, and annotated code. Each demo maps to a specific narrative takeaway.

Reads: Narrative brief and content creator's assets via the unit's ## References section.

Anti-patterns (RFC 2119):

  • The agent MUST NOT create demos that require undocumented environment setup
  • The agent MUST NOT build fragile demos that break under live conditions
  • The agent MUST NOT hardcode secrets, API keys, or environment-specific paths
  • The agent MUST NOT skip error handling that would cause confusing failures during presentation
  • The agent MUST verify that each demo runs end-to-end from a clean environment

Review Agents

Engagement

Mandate: The agent MUST verify content is compelling and structured for developer engagement.

Check:

  • The agent MUST verify that content follows the narrative arc and delivers the promised takeaways
  • The agent MUST verify that the hook grabs developer attention within the first paragraph or slide
  • The agent MUST verify that content format is appropriate for the target platform and audience segment
  • The agent MUST verify that calls-to-action are clear and the reader knows what to do next

Technical Accuracy

Mandate: The agent MUST verify all technical content is accurate, runnable, and trustworthy.

Check:

  • The agent MUST verify that code examples compile and run without errors
  • The agent MUST verify that demos are reproducible from a clean environment with documented setup
  • The agent MUST verify that technical claims are substantiated by working examples, not hand-waving
  • The agent MUST verify that API references, version numbers, and configuration details are current

Create

Criteria Guidance

Good criteria examples:

  • "Blog post includes working code examples that the reader can copy-paste and run"
  • "Talk slides follow a narrative arc with no slide exceeding 3 bullet points"
  • "Demo runs end-to-end without manual setup steps beyond what the README documents"

Bad criteria examples:

  • "Content is created"
  • "Demo works"
  • "Slides look good"

Completion Signal (RFC 2119)

Content package MUST exist with all planned assets produced and technically verified. Code examples MUST compile and run. Demo builder MUST have validated that all demos are reproducible from a clean environment. Content creator MUST have verified that each asset follows the narrative arc and delivers the key takeaways defined in the narrative brief.