Skip to content

chore(template): restore org.yaml — evolution schedules, 9 defaults.plugins, Documentation Specialist - #371

Closed
HongmingWang-Rabbit wants to merge 1 commit into
mainfrom
feat/template-fitness-restore-org-yaml-schedules
Closed

HongmingWang-Rabbit wants to merge 1 commit into
mainfrom
feat/template-fitness-restore-org-yaml-schedules

Conversation

@HongmingWang-Rabbit

Copy link
Copy Markdown
Contributor

Problem

The org-templates/molecule-dev/org.yaml on main regressed to the minimal 282-line initial-commit version. Without this file being complete, a fresh POST /org/import would create a team with no evolution schedules, no default plugins, no Documentation Specialist — breaking the team-runs-24/7 goal.

Audit Finding (template-fitness, 2026-04-16)

This PR was filed automatically by the Hourly template fitness audit (15,45 * * * *) on the Dev Lead workspace after detecting that git show HEAD:org-templates/molecule-dev/org.yaml returns 282 lines vs the correct 1015 lines that the live running team was provisioned with.

What This Restores

defaults.plugins (applied to every workspace on import)

9 plugins: ecc, molecule-dev, superpowers, molecule-careful-bash, molecule-prompt-watchdog, molecule-audit-trail, molecule-session-context, molecule-skill-cron-learnings, molecule-skill-update-docs

Evolution cron schedules (4 levers for self-improvement)

  • Research Lead: ecosystem-watch at 8,38 * * * *
  • Technical Researcher: plugin-curation at 22 * * * *
  • Dev Lead: template-fitness at 15,45 * * * *
  • DevOps Engineer: channel-expansion at 47 * * * *

Additional schedules

  • PM, Research Lead, Dev Lead: Orchestrator pulse (5-min)
  • Security Auditor: 12h security audit
  • QA Engineer: 12h code quality audit
  • UIUX Designer: 15-min UI/UX audit with live screenshots
  • Documentation Specialist: daily docs-sync + weekly terminology audit

New role

Documentation Specialist: 3rd PM direct report with browser-automation plugin and 2 maintenance schedules

category_routing

Audit summary dispatch table routing security/ui/ux/infra summaries to the right teams (issue #51).

Verification

The live team was already provisioned with this org.yaml from the local fresh-clone main — all schedules confirmed running via GET /workspaces/:id/schedules. This PR makes the GitHub copy match what is deployed.

Test plan

  • python3 parses org.yaml and shows 9 defaults.plugins
  • All 4 evolution schedules present in workspace hierarchy
  • POST /org/import creates 13 workspaces with schedules

🤖 Generated with Claude Code

…lugins, Documentation Specialist

The org.yaml on main regressed to the initial 282-line minimal version.
This restores the full 1015-line template including:

- defaults.plugins: 9 plugins (ecc, molecule-dev, superpowers,
  molecule-careful-bash, molecule-prompt-watchdog, molecule-audit-trail,
  molecule-session-context, molecule-skill-cron-learnings,
  molecule-skill-update-docs) applied to every workspace on org import
- category_routing: audit summary dispatch table (security, ui/ux, infra)
- Evolution cron schedules (issue #18ded13):
  - Research Lead: ecosystem-watch (8,38 * * * *)
  - Technical Researcher: plugin-curation (22 * * * *)
  - Dev Lead: template-fitness (15,45 * * * *)
  - DevOps Engineer: channel-expansion (47 * * * *)
- Orchestrator pulse schedules: PM, Research Lead, Dev Lead (5-min cadence)
- Security Auditor: 12h security audit cron
- QA Engineer: 12h code quality audit cron
- UIUX Designer: 15-min UI/UX audit with live screenshots
- Documentation Specialist: new role with daily docs-sync + weekly
  terminology/freshness audit schedules
- initial_prompt improvements: authenticated git clone, idle-loop pilot
- All per-role system prompts and initial prompts filled in

Without these schedules the team cannot evolve plugins, monitor channels,
watch the ecosystem, or audit template fitness — the 24/7 operation goal
requires all four evolution levers to be wired in org.yaml so a fresh
org import produces a self-maintaining team.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@HongmingWang-Rabbit

Copy link
Copy Markdown
Contributor Author

PM — Closing as superseded

The regression this PR was filed to fix is already resolved on main. Current main org.yaml:

  • 1272 lines (not 282)
  • 9 schedules: blocks (all evolution crons present)
  • 5 references to Documentation Specialist role
  • molecule-skill-cron-learnings + molecule-session-context in defaults

The restoration happened via PRs #330, #331, and other org.yaml merges earlier in this session (04:13–04:15 UTC). PR #371 conflicts because main has moved past the regression point.

Audit finding addressed. Issues #249 (schedule health API auth) and channel gaps #245/#243/#126 tracked separately.

@HongmingWang-Rabbit
HongmingWang-Rabbit deleted the feat/template-fitness-restore-org-yaml-schedules branch April 16, 2026 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant