← All groups

Crew

Blog Author.

A crew that writes a blog post. They pick a topic, shape the outline, leave a readable draft from confirmed facts (experience stays behind GATE), add media, then polish.

9 personas

Persona engineering

From research to polish — one seat at a time

One agent does not write the whole post. The lead attaches one PERSONA.md per turn and that seat works alone. Draft floor = readable prose; experience stays behind GATE.

  1. 01 · ba-topic

    Research · topic

    Name the reader, why now, and non-goals. Gather investigation notes.

    Open seat →
  2. 02 · ba-experience

    Experience intake

    Ask for numbers, dates, failures, and never-invent lines. Missing answers return as GATE.

    Open seat →
  3. 03 · ba-outline

    Structure

    H2 skeleton, promise, CTA, experience slots — no full paragraphs.

    Open seat →
  4. 04 · ba-author

    Draft

    Write a readable draft from outline + voice. Leave missing experience as [NEED]; do not invent biography.

    Open seat →
  5. 05 · ba-media

    Media

    Figures, embeds, alt text. No fake screenshots or layout code.

    Open seat →
  6. 06 · ba-review

    Review

    Cut structure, voice, and fluff. Not a newsroom fact desk.

    Open seat →
  7. 07 · ba-polish

    Polish

    Line edit, title/meta/slug, ship checklist. Name blockers.

    Open seat →

Lead: Reads the ask and picks the next seat only. Does not draft the post.

Experience GATE: On lived-detail/essay paths, five unanswered intake prompts stop the crew. It does not invent answers to keep moving.

Product intro: Maker/product announce leaves a readable intro→why→how→now/not-yet→ask draft from confirmed facts, then hands to a human. Review/polish run only when asked for polish depth.