Weekly Community Publisher

A prompt-driven editorial workflow for collecting weekly community signal, drafting the roundup, and shipping it with human review, without pretending there is a packaged bundle behind it yet.

Classification

Conceptual workflow

Install mode

Prompt-driven

Review status

Concept review

Verification mode

Concept review

This listing does not point to a real bundle directory or installable external package yet. It describes a supervised workflow that currently starts from a prompt plus operator-managed notes.

openclaw agent run --prompt "Draft and stage the weekly community roundup using the publishing workflow"

Bundle id

superada.workflow.weekly-community-publisher

Entrypoint

editorial prompt

Bundle root

prompt-driven workflow, not yet packaged

Artifact count

4 described items

A lightweight editorial workflow pattern that packages the recurring roundup process conceptually, while keeping installation and artifacts honest.

Installability

Not installable yet

Method

Prompt-run workflow

openclaw agent run --prompt "Draft and stage the weekly community roundup using the publishing workflow"

Draft and stage the weekly community roundup using the publishing workflow

1. 1
   Step 1 Gather weekly source material

   Assemble the links, notes, and candidate items that should feed the weekly roundup.

2. 2
   Step 2 Run the drafting prompt

   Launch the workflow manually to create or update the roundup draft.

   Copy

   openclaw agent run --prompt "Draft and stage the weekly community roundup using the publishing workflow"

3. 3
   Step 3 Review and publish by hand

   Edit the draft, confirm links and tone, then commit or publish only after human review.

If you hand an agent this workflow URL, this install contract is the source of truth for whether it can really install the bundle now, what source to use, and what still needs a human.

• Editorial run prompt prompt
  prompt:Draft and stage the weekly community roundup using the publishing workflow

  Operator-launched prompt that frames the roundup draft and staging work.

• Source collection notes concept
  operator-managed weekly links and notes

  Human-curated sources that seed the publishing run before the draft is generated.

• Draft article output doc
  src/content/blog/<weekly-roundup>.mdx

  The intended draft output staged for editorial review and later publication.

• Publish checklist concept concept
  editorial review checklist

  Manual approval layer that confirms tone, links, and formatting before publish.

• Editorial source material review

  The workflow needs a real pool of links, notes, and community signal to summarize.

• Site content access access

  The operator needs permission to stage or edit blog content in the site repo.

• Human editorial approval review

  Publishing stays supervised in v1, especially for tone, accuracy, and headline quality.

Verification language now matches reality. Installable bundles can be tested after install, external bundles should be source-reviewed first, and conceptual entries are reviewed as designs until real artifacts exist.

1. 1
   Prompt run produces a draft

   Confirm the workflow produced a concrete article draft or staged content update.

   Expected: A publishable draft file or working draft is ready for human review.

2. 2
   Editorial review complete

   Read the article end to end and fix voice, accuracy, and formatting before publish.

   Expected: A reviewed draft that can be committed without obvious factual or stylistic issues.

• Review links, names, and claims before shipping.
• Confirm the final article matches the week's actual themes instead of generic filler.
• Treat generation as draft acceleration, not autonomous publishing.

• Weekly ecosystem updates
• Community report generation
• Editorial ops that should not start from zero each Monday

• This is currently a prompt-driven workflow pattern, not a packaged local or external bundle.