Comprehensive rewrite of the Molecule AI dev team org template:
- Rename agents to {team}-{role} convention (e.g., core-be, cp-lead, app-qa)
- Add 5 new team leads: Core Platform Lead, Controlplane Lead, App & Docs Lead, Infra Lead, SDK Lead
- Add new roles: Release Manager, Integration Tester, Technical Writer, Infra-SRE, Infra-Runtime-BE, SDK-Dev, Plugin-Dev
- Delete triage-operator and triage-operator-2 (leads own triage now)
- Set default model to MiniMax-M2.7, tier 3, idle_interval_seconds 900
- Update org.yaml category_routing to new agent names
- Add orchestrator-pulse schedules for all leads (*/5 cron)
- Add pick-up-work schedules for engineers (*/15 cron)
- Add qa-review schedules for QA agents (*/15 cron)
- Add security-scan schedules for security agents (*/30 cron)
- Add release-cycle and e2e-test schedules for Release Manager and Integration Tester
- Update marketing agents with web search MCP and media generation capabilities
- All schedule prompts reference Molecule-AI/internal for PLAN.md and known-issues.md
- Un-ignore org-templates/molecule-dev/ in .gitignore for version tracking
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
843 B
843 B
IMPORTANT: Check Molecule-AI/internal repo for roadmap (PLAN.md), known issues (known-issues.md), runbooks before starting work.
QA review cycle. Be thorough and incremental.
- Pull latest on your assigned repos.
- Check what you audited last time: use search_memory("qa audit").
- See what changed since last audit.
- Run ALL test suites and record results.
- Check test coverage on recently changed files.
- Review recent PRs for quality issues and test gaps.
- Check for regressions (run builds, look for errors).
- Record findings to memory.
DELIVERABLE ROUTING (MANDATORY every cycle): a. For each failing test or coverage regression: FILE A GITHUB ISSUE. b. delegate_task to your team lead with a summary. c. If all clean: delegate_task with "qa clean on SHA ". d. Save to memory key "qa-audit-latest" as secondary record.