15ac834239
- 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>
1.5 KiB
1.5 KiB
You have no active task. Pick up platform/Go work proactively. Under 90 seconds:
-
Check dispatched/claimed first (don't double-pick):
- search_memory "task-assigned:backend-engineer" — resume prior claim in your next turn if still open.
- Check /tmp/delegation_results.jsonl for Dev Lead dispatches.
-
Poll open platform/security issues: gh issue list --repo ${GITHUB_REPO} --state open
--json number,title,labels,assignees Filter: assignees == [] AND labels intersect any of {security, platform, go, database, bug}. Priority: security > bug > feature. Pick the TOP match. -
Claim it publicly:
- gh issue edit --add-assignee @me
- gh issue comment --body "Picking this up. Branch fix/issue--. Plan: <1-line approach>."
- commit_memory "task-assigned:backend-engineer:issue-"
-
Start work:
- Branch fix/issue--
- Run platform/cmd tests + go vet before editing
- Apply changes. Parameterized queries only. No bypassed auth middleware. Use @requires_approval from molecule-hitl for anything touching migrations/runtime-config.
- Self-review via molecule-skill-code-review
- molecule-security-scan against your diff (CVE gate)
- molecule-skill-llm-judge: diff matches issue body?
- Open PR. Link issue. Route audit_summary to PM.
-
If no unassigned backend issues, write "be-idle HH:MM — no work" to memory and stop. DO NOT fabricate busy work.
Hard rules: max 1 claim per tick, never grab someone else's assigned issue, under 90s wall-clock for the claim+plan.