2.3 KiB
2.3 KiB
Skill Workspace Monorepo Migration
Status
completed
Owner
- Codex
Started At
2026-03-20
Goal
- Execute
Milestone 10: Skill Workspace Monorepo Migrationby moving the repository toward a true multi-package monorepo whose primary deliverables are skills and skill runtimes.
Scope
- bootstrap the shared workspace structure described in
docs/skill-workspace-monorepo.md - complete migration phases incrementally, committing after each completed phase
- keep packaging, roadmap, and validation flows synchronized as the migration proceeds
Checklist
- create or adopt an active execution roadmap for the migration workstream
- Phase 1: bootstrap
go.work, expanded workspace manifests, package roots, and declarative skill bundle metadata - Phase 2: extract shared coordination code into
packages/coord-core - Phase 3: extract
inbox-runtimeandorch-runtime - Phase 4: extract
orchd-runtime - Phase 5: import
repo-memory-runtimeand addskills/repo-memory - Phase 6: remove root runtime ownership and normalize package-based packaging
Files
docs/roadmaps/archive/skill-workspace-monorepo-migration.mddocs/skill-workspace-monorepo.mddocs/implementation-roadmap.mdgo.workpnpm-workspace.yamlpackage.jsonpackages/scripts/
Decisions
- keep one long-lived active roadmap for the full migration rather than opening a new execution trace for every individual phase
- complete and commit one migration phase at a time so the workspace remains bisectable
Blockers
- none
Next Step
- resume product work on top of the package-owned runtime workspace, starting with whichever user-facing feature slice has priority next
Completion Summary
- bootstrapped the repository as a multi-package workspace with
go.work, expanded JS workspace discovery, and declarative skill bundle metadata - extracted the shared coordination kernel into
packages/coord-core - extracted package-owned runtimes for
inbox,orch,orchd, andrepo-memory - switched the root skill packaging flow to build from package entrypoints, including the new
repo-memorybundle - removed the legacy root runtime implementation directories under
internal/, leaving rootcmd/*as compatibility shims while package-owned runtimes remain the source of truth