forked from molecule-ai/molecule-core
f5b81710df
2 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
f075c49af1 |
feat(org-templates): Phase 2 — bulk migrate 20 roles to file-ref prompts (#395)
Part 2 of 4 in the org.yaml scalability refactor. Follows PR #389 which added platform support; this PR completes the migration for every role in the `molecule-dev` template. ## Scope All 20 remaining roles moved from inline YAML literals to sibling .md files under their existing `files_dir`: - PM, Research Lead, Dev Lead, Marketing Lead (4 leaders) - Market Analyst, Technical Researcher, Competitive Intelligence (research) - Frontend/Backend/DevOps Engineer, Security Auditor, QA Engineer, UIUX Designer, Triage Operator (dev team) - DevRel, PMM, Content Marketer, Community Manager, SEO Growth Analyst, Social Media Brand (marketing team) Per workspace, externalized (where present): - `initial_prompt: |...` → `initial-prompt.md` + `initial_prompt_file:` - `idle_prompt: |...` → `idle-prompt.md` + `idle_prompt_file:` - `schedules[*].prompt: |...` → `schedules/<slug>.md` + `prompt_file:` Totals: 17 initial-prompt files, 12 idle-prompt files, 18 schedule files (47 new files). ## File-size impact | Before (main) | After Phase 1 | After Phase 2 | Reduction | |---|---|---|---| | 1801 lines | 1687 lines | 676 lines | **-62.5%** | | 108 KB | 101 KB | 35 KB | **-67%** | org.yaml is now pure structural scaffolding (name / role / tier / model / canvas / plugins / channels / children / category_routing / schedules metadata). Readable end-to-end on one screen per team. ## How the migration was driven A Python round-trip script (using `ruamel.yaml` to preserve comments + formatting) walked the workspace tree recursively, wrote prompts to files keyed by `files_dir`, and replaced inline keys with `*_file:` refs. Zero manual YAML hand-editing beyond the Phase 1 Documentation Specialist proof. Script is one-shot; not committed. Slug convention for schedule files: lowercase the schedule name, replace non-alphanumeric with `-`, collapse, cap 60 chars. Examples: - "Orchestrator pulse" → `orchestrator-pulse.md` - "Hourly template fitness audit" → `hourly-template-fitness-audit.md` - "Code quality audit (every 12h)" → `code-quality-audit-every-12h.md` ## Backwards compatibility Fully compatible — Phase 1's resolver prefers inline when both are set, so a future one-off experiment can still drop inline YAML. The migration doesn't remove inline support, just stops using it. ## Verification - [x] `python -c "yaml.safe_load(...)"` on edited org.yaml — parses clean - [x] Walk-and-inspect script: every workspace has exactly the expected `*_file:` refs, zero `INLINE_*` markers remain - [x] All 47 extracted .md files non-empty + trimmed - [x] `go test -run 'TestResolvePromptRef|TestOrgYAML|TestInitialPrompt'` passes (from Phase 1 platform work) - [ ] Post-merge: live `POST /org/import` against a fresh workspace, diff the resulting `/configs/config.yaml` + `workspace_schedules` rows against the pre-migration values (should be identical bodies) ## What's next - **Phase 3 (queued):** YAML `!include` directive for org.yaml; split the remaining 676 lines into `teams/{research,dev,marketing,ops}.yaml`. - **Phase 4 (queued):** per-workspace atomization; each role owns its own `workspace.yaml` manifest. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|
|
592fe6d7f7 |
feat(org-templates): add 7-role marketing team sub-tree (#373)
Add Marketing Lead + 6 reports as a peer sub-tree of PM under the CEO: DevRel Engineer, Product Marketing Manager, Content Marketer, Community Manager, SEO Growth Analyst, Social Media / Brand. - Marketing Lead: tier-3 Opus CMO-equivalent with a 5-min orchestrator pulse (minutes 4/9/14/... offset from Dev Lead's 2/7/12/...) that dispatches cross-role work, reviews drafts, and routes cross-team asks back to PM. - DevRel + PMM: tier-3 Opus (technical writing + positioning judgment). Each has an idle_prompt for proactive issue-claim plus an hourly evolution cron (DevRel = sample-coverage audit, PMM = competitor diff against docs/ecosystem-watch.md). - Content / Community / SEO / Social: tier-2 Sonnet with idle_prompts for backlog-pull (matches the #205 idle-loop pattern proven on Technical Researcher + Market Analyst + Competitive Intelligence). Each has an hourly cron tuned to its surface. - category_routing gets 6 new keys (content, positioning, community, growth, social, devrel) so audit_summary messages fan out correctly. - Canvas positions lay out the marketing cluster to the right of PM/Dev Lead (x=1000-1300, y=50/250/400) so the graph stays readable. Each role also gets a system-prompt.md under its files_dir with responsibilities, team interfaces, conventions, and self-review gates (molecule-skill-llm-judge or molecule-hitl depending on risk). Per CEO directive 2026-04-16 ("comprehensive marketing team"). This is PR 1 of 2 — follow-up will add cross-tree A2A conventions and wire DevRel ↔ Backend Engineer / PMM ↔ Competitive Intelligence delegations. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |