by kimseungmin
Project environment & structure governance harness — knows your local directory like a second brain. Ships generic, specializes to your project the more you use it: scans structure, codifies naming/layout rules, organizes files safely, tracks datasets (checksum/split/lineage), governs Docker environment assets (generates Dockerfile/compose into .omp/env/, image naming + inventory, anti-pattern audit with external-standard provenance), learns project-specific rules over time, and — as of 0.4.0 — adds a secretary axis (time): session journal, todo/RAID, decisions, and pull-style briefing under .omp/secretary/, written by a single scoped agent and derived-only status (no LLM-estimated progress, no auto-closed tasks). 0.5.0 anchors the secretary to existing state surfaces (rules.json secretary.sources[] read-map — Kanban/daily-notes/status tables registered via the codify gate, counts derived never estimated) and adds delegation briefing (omp-handoff: a 4-element knowledge packet assembled before handing work to a sibling harness such as oms/omd/omx). 0.8.0 adds a registry axis (rules.json code_graphs.indexes[] — local code indexes registered as READ targets with their real coverage, a warn-default audit axis for stale/coverage-mismatch, inbound-import counts in organize dry-runs, and coverage carried into the handoff packet; omp registers and verifies but never builds an index). 0.9.0 adds omp-style, which induces code idioms from existing source (file anatomy, state/control-flow naming, infrastructure placement, error/logging shape) with a 3-witness floor and a measured violation count, then proposes them into the existing content_conventions[] axis through the codify gate — no new schema field, and it never edits source. SSOT lives in a hidden .omp/ folder (human .md + machine .json).
Claude Code16 Skills