molecule-ai/molecule-core
35
0
Fork 2
Code Issues 16 Pull Requests 2 Actions 49 Packages Projects Releases Wiki Activity
15ac834239
molecule-core/org-templates/molecule-dev/dev-lead/schedules/hourly-template-fitness-audit.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

2.0 KiB
Raw Blame History

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

Daily audit of org-templates/molecule-dev/. Catches drift, stale prompts, missing schedules, and gaps that block the team-runs-24/7 goal. Symptom of prior incident (issue #85): cron scheduler died silently for 10+ hours and nobody noticed because no one was watching template fitness.

  1. CHECK SCHEDULES ARE FIRING: For every workspace_schedule in the platform DB: curl -s http://host.docker.internal:8080/workspaces//schedules Compare last_run_at to now() vs cron interval. Anything more than 2x the interval behind = STALE. File issue against platform.

  2. CHECK SYSTEM PROMPTS ARE FRESH: cd /workspace/repo for f in org-templates/molecule-dev/*/system-prompt.md; do echo "$(git log -1 --format='%ar' -- "$f") $f" done Anything not touched in 30+ days might be stale relative to recent platform changes. Spot-check vs CLAUDE.md and recent merges.

  3. CHECK ROLES HAVE PLUGINS THEY NEED: yq '.workspaces[] | (.name, .plugins)' org-templates/molecule-dev/org.yaml (or python+yaml). Roles inherit defaults; flag any role that should plausibly have role-specific extras (compare role description vs plugins list).

  4. CHECK CRONS COVER THE EVOLUTION LEVERS: The team must keep evolving plugins, template, channels, watchlist. Verify schedules exist for: ecosystem-watch (Research Lead), plugin-curation (Technical Researcher), template-fitness (you, this cron), channel-expansion (DevOps). Any missing? File issue.

  5. CHECK CHANNELS: Today only PM has telegram. Should any other role have a channel? (Security Auditor → email on critical findings; DevOps → Slack on build breaks; etc.) File issue if a channel gap is meaningful.

  6. ROUTING: delegate_task to PM with audit_summary metadata (category=template, severity=…, issues=[…], top_recommendation=…).

  7. If everything is fit and current, PM-message one-line "clean".