molecule-ai/molecule-core
34
0
Fork 2
Code Issues 16 Pull Requests 2 Actions 49 Packages Projects Releases Wiki Activity
dae7f50095
molecule-core/org-templates/molecule-dev/devops-engineer/schedules/hourly-channel-expansion-survey.md
rabbitblood 15ac834239 feat(template): expand dev team to 30+ roles with multi-repo coverage 
- org.yaml: Remove required_env (PR #1031), update category_routing for new roles
- New workspace roles (9): backend-engineer-3, frontend-engineer-2/3, fullstack-engineer,
  platform-engineer, qa-engineer-2/3, security-auditor-2, triage-operator-2
- Wire existing backend-engineer-2 and sre-engineer into teams/dev.yaml hierarchy
- Triage operators: add MERGE AUTHORITY as #1 priority, multi-repo coverage
- Security auditor: multi-repo rotation across all org repos
- QA: dedicated coverage for controlplane+proxy and app+docs
- Marketing schedules: add TTS, music, lyrics, image, video capabilities
- Research sub-agents: add */30 research/competitor/market cycles with web_search
- All schedules: add "IMPORTANT: Check internal repo" directive
- Leader pulses: expanded team scan to include all new roles
- Dev-lead: updated dispatch mapping for 16 engineering roles

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-20 00:29:56 -07:00

1.5 KiB
Raw Blame History

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

Weekly survey of channel integrations (Telegram, Slack, Discord, email, webhooks). The team should grow its external comms surface where useful, not stay locked at "PM-only Telegram".

  1. INVENTORY: yq '.workspaces[] | {name: .name, channels: .channels}'
    org-templates/molecule-dev/org.yaml 2>/dev/null (or python+yaml). List which roles have which channels.
  2. PLATFORM CAPABILITY CHECK: grep -rE "channel|telegram|slack|discord|webhook"
    platform/internal/handlers/ --include="*.go" -l What channel types does the platform actually support today?
  3. GAP ANALYSIS:
    • PM has Telegram → can the user reach OTHER roles directly?
    • Security Auditor: would email-on-critical-finding help?
    • DevOps Engineer: would Slack-on-CI-break help?
    • Any role that produces high-value asynchronous output but the user has to poll memory to see it?
  4. EXTERNAL: are there channel platforms we should consider adding? (Discord for community, GitHub Discussions for product, etc.)
  5. For the top 1-2 gaps, file a GH issue:
    • "Channel proposal: for " with rationale, integration sketch, secret requirements (e.g. SLACK_BOT_TOKEN as global secret).
  6. ROUTING: delegate_task to PM with audit_summary metadata (category=channels, issues=[…], top_recommendation=…).
  7. If no gap this week, PM-message a one-line "clean".