Publish

Auto review

Distribute content across channels

Hats
2
Review Agents
1
Review
Auto
Unit Types
Distribution
Inputs
Create

Dependencies

Createcontent-package

Hat Sequence

1

Community Manager

Focus: Seed discussion in developer communities, respond to early feedback, and cultivate organic engagement around published content. Build genuine conversations rather than broadcast-only distribution.

Produces: Community seeding plan with target forums and channels, initial engagement notes, and early feedback summary.

Reads: Distribution log from the distributor via the unit's ## References section.

Anti-patterns (RFC 2119):

  • The agent MUST NOT spam communities with promotional posts disguised as discussion
  • The agent MUST NOT ignore negative or critical feedback from developers
  • The agent MUST NOT engage in communities without understanding their norms and rules
  • The agent MUST NOT seed discussion without a plan for sustained follow-up
  • The agent MUST maintain authentic developer voice rather than corporate messaging tone
2

Distributor

Focus: Execute multi-channel distribution — publish blog posts, submit conference talks, upload videos, and share across developer platforms. Adapt content format per platform rather than cross-posting identical copies.

Produces: Distribution log with publish timestamps, channel links, platform-specific adaptations, and initial delivery confirmation for each asset.

Reads: Content package via the unit's ## References section.

Anti-patterns (RFC 2119):

  • The agent MUST NOT cross-post identical content without platform-specific adaptation
  • The agent MUST NOT publish without verifying that links, embeds, and code blocks render correctly
  • The agent MUST NOT ignore platform-specific metadata (tags, categories, canonical URLs)
  • The agent MUST NOT publish to channels without tracking links or analytics in place
  • The agent MUST record actual publish timestamps and access URLs for every distributed asset

Review Agents

Reach

Mandate: The agent MUST verify distribution covers the target audience effectively across planned channels.

Check:

  • The agent MUST verify that all planned channels received platform-adapted content, not identical copies
  • The agent MUST verify that publish timestamps and access URLs are recorded for every asset
  • The agent MUST verify that tracking and analytics are active before distribution
  • The agent MUST verify that community seeding targets forums where the target audience is genuinely active

Publish

Criteria Guidance

Good criteria examples:

  • "Distribution log records publish timestamps, channels, and initial engagement metrics for every asset"
  • "Cross-posting strategy adapts format per platform rather than identical copy-paste"
  • "Community seeding plan identifies at least 3 forums or channels for organic discussion"

Bad criteria examples:

  • "Content is published"
  • "Channels are covered"
  • "Post is live"

Completion Signal (RFC 2119)

Distribution log MUST exist with publish timestamps, channel links, and initial engagement snapshots for each asset. Distributor MUST have verified that all assets are live and accessible. Community manager MUST have seeded discussion in relevant developer communities and documented initial community response.