Files
stack/skills/mosaic-standards/SKILL.md
Mos (Agent) 10689a30d2
Some checks failed
ci/woodpecker/push/ci Pipeline failed
ci/woodpecker/pr/ci Pipeline failed
feat: monorepo consolidation — forge pipeline, MACP protocol, framework plugin, profiles/guides/skills
Work packages completed:
- WP1: packages/forge — pipeline runner, stage adapter, board tasks, brief classifier,
  persona loader with project-level overrides. 89 tests, 95.62% coverage.
- WP2: packages/macp — credential resolver, gate runner, event emitter, protocol types.
  65 tests, 96.24% coverage. Full Python-to-TS port preserving all behavior.
- WP3: plugins/mosaic-framework — OC rails injection plugin (before_agent_start +
  subagent_spawning hooks for Mosaic contract enforcement).
- WP4: profiles/ (domains, tech-stacks, workflows), guides/ (17 docs),
  skills/ (5 universal skills), forge pipeline assets (48 markdown files).

Board deliberation: docs/reviews/consolidation-board-memo.md
Brief: briefs/monorepo-consolidation.md

Consolidates mosaic/stack (forge, MACP, bootstrap framework) into mosaic/mosaic-stack.
154 new tests total. Zero Python — all TypeScript/ESM.
2026-03-30 19:43:24 +00:00

1003 B

name, description
name description
mosaic-standards Load machine-wide Mosaic standards and enforce the repository lifecycle contract. Use at session start for any coding runtime (Codex, Claude, OpenCode, etc.).

Mosaic Standards

Load Order

  1. ~/.config/mosaic/STANDARDS.md
  2. Repository AGENTS.md
  3. Repo-local .mosaic/repo-hooks.sh when present

Session Lifecycle

  • Start: scripts/agent/session-start.sh
  • Priority scan: scripts/agent/critical.sh
  • End: scripts/agent/session-end.sh

If wrappers are available, you may use:

  • mosaic-session-start
  • mosaic-critical
  • mosaic-session-end

Enforcement Rules

  • Treat ~/.config/mosaic as canonical for shared guides, tools, profiles, and skills.
  • Do not edit generated project views directly when the repo defines canonical data sources.
  • Pull/rebase before edits in shared repositories.
  • Run project verification commands before claiming completion.
  • Use non-destructive git workflow unless explicitly instructed otherwise.