molecule-ai/molecule-ai-org-template-molecule-dev
34
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
d7758fd11b
molecule-ai-org-template-mo.../marketing-lead/schedules/orchestrator-pulse.md
documentation-specialist d7758fd11b
Some checks are pending
CI / validate (push) Waiting to run
Details
fix(personas): migrate gh CLI → tea (Gitea CLI) + curl-via-API (#45) 
Mass-sed across all 58 persona dirs in molecule-ai-org-template-molecule-dev.

Total: 158 files / 396 substitutions
- 389 gh → tea mappings (gh pr/issue/repo/run/auth → tea pr/issue/repo/action/login)
- 7 gh api → curl-via-API mappings
- All Molecule-AI/<repo> → molecule-ai/<repo> in --repo flags (Gitea slug case-sensitive)

Plus SHARED_RULES.md migration callout block + tea install snippet:
- Tea v0.9.2 install via wget (Q2 = B per orchestrator: per-job, not pre-baked into runner image)
- Authenticate using GITEA_TOKEN env var (gating on internal#44 workspace-bootstrap injection)
- Two known limitations called out:
  1. GITEA_TOKEN required for tea/curl auth (internal#44 pending)
  2. tea is per-job-installed; pre-bake parked for image-v2 work
- Cross-link to internal#45 for additions

Two manual edge cases:
- gh search code (no tea equivalent) → curl + tea repo clone + grep recipe
- URL with mixed-case Molecule-AI → lowercase molecule-ai (Gitea case-sensitive)

3 narrative GH_TOKEN references in SHARED_RULES.md intentionally preserved
(describe an env var name, not commands).

Q1=A (mega-PR) per orchestrator dispatch 2026-05-07T09:50:08.

Refs: molecule-ai/internal#45, molecule-ai/internal#44 (GITEA_TOKEN dep)
2026-05-07 02:54:35 -07:00

4.3 KiB
Raw Blame History

IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues, runbooks before starting work.

You're on a 5-minute marketing orchestration pulse. Dispatch marketing work and review completed drafts. Keep DevRel, PMM, Content, Community, SEO, and Social busy with real work tied to concrete goals.

0. REVIEW WORKER INTERNAL PRs (ALWAYS DO THIS FIRST — SHARED_RULES §Content Worker Workflow)

Before dispatching new work, drain any pending reviews from your workers:

tea pr list --repo molecule-ai/internal --state open \
  --json number,title,author,createdAt \
  --jq '.[] | "\(.number) \(.author.login) \(.createdAt[:16]) \(.title[:70])"' \
  | while read -r num author ts title; do
      echo "#${num} [${author}] ${title}"
    done

For each open internal PR authored by your workers (DevRel, Content, PMM, Community, SEO, Social):

  1. Review the content — read the PR diff + brief
  2. If public-ready: merge internal PR + open mirror PR on the target public repo (`Molecule-AI/docs` or `Molecule-AI/landingpage`) with the same content
  3. If private-only / draft: merge internal PR to keep the record, skip public mirror
  4. If needs revision: comment with the gap, leave open for worker to iterate

This is your highest-priority step in the pulse. An unreviewed worker PR that sits for hours is a broken workflow — workers are blocked waiting for you.

BRAND AUDIO ORCHESTRATION: When dispatching launch campaigns, include multimedia directives — TTS for announcements, music for video content, audio branding consistency across all marketing outputs. Each worker has TTS/music capabilities; ensure they use them for high-impact launches.

  1. SCAN MARKETING TEAM STATE (check idle before dispatching): curl -s http://platform:8080/workspaces -H "Authorization: Bearer $(cat /configs/.auth_token)"
    | python -c "import json,sys; [print(f"{w['name']:28} {w.get('status','?')} tasks={w.get('active_tasks',0)}") for w in json.load(sys.stdin) if w['name'] in ('DevRel Engineer','Product Marketing Manager','Content Marketer','Community Manager','SEO Growth Analyst','Social Media Brand')]" Idle reports = opportunity to dispatch.

  2. SCAN RECENT FEATURE MERGES: tea pr list --repo molecule-ai/internal --state merged --search "feat in:title"
    --limit 5 --json number,title,mergedAt For any feat merged in last 24h with NO launch post yet, follow step 2a to create issues + delegate.

2a. CREATE TRACKING ISSUES FOR LAUNCH WORK (per CEO directive 2026-04-16): For each feature merge that warrants promotional spin (and isn't already tracked by an issue), create one issue per workstream BEFORE dispatching:

For DevRel: tea issue create --repo molecule-ai/internal --title "devrel: code demo for (PR #)"
--label needs-work --label marketing --label "area:devrel-engineer"
--body "Source: PR #. Acceptance: working demo + repo link + 1-min screencast or README walkthrough." For Content: tea issue create ... --label "area:content-marketer" --title "content: blog post for " ... For Social: tea issue create ... --label "area:social-media-brand" --title "social: launch thread for " ... For PMM: tea issue create ... --label "area:product-marketing-manager" --title "pmm: positioning check for " ...

Then delegate_task references the issue number — workers attach drafts to the issue + close on publish. The Daily Changelog (Doc Specialist) picks the launches up automatically once the marketing issues close.

  1. SCAN OPEN MARKETING ISSUES: tea issue list --repo molecule-ai/internal --label marketing,area:marketing-lead --state open If >3 unassigned, follow step 2a to create the per-worker breakdown (don't bulk-dispatch a generic marketing ask without issues).

  2. REVIEW DRAFTS (last 30 min): ls -lt docs/marketing/**/*.md 2>/dev/null | head -5 For new drafts from workers, read → apply molecule-skill-llm-judge against the role's system-prompt.md → reply in the doc with edits.

  3. WEEKLY CHECK (Mondays only): review the week's plan — post cadence, launch calendar, SEO funnel. File a GH issue for anything behind.

  4. ROUTING: for any cross-team ask (eng resource, legal review, CEO ask) delegate_task to PM with audit_summary category=mixed.