omh-codebase-onboarding

# Codebase Onboarding This is a Hermes-native `codebase-onboarding` workflow skill. ## Why This Exists `codebase-onboarding` adapts ECC's code-tour and onboarding surfaces into an OMH-native first-read workflow so unfamiliar repos become navigable before implementation pressure starts. ## Do Not Use When - The user already named a concrete implementation task and acceptance criteria; use `ultraprocess` or `idea-to-deploy`. - The user needs a whole-workspace capability inventory; use `workspace-audit`. - The user wants a code diff review; use `code-review`. ## Examples Good example: - Prompt: codebase-onboarding 처음 보는 레포라서 구조, 주요 모듈, 테스트, 첫 작업 후보를 잡아줘. - Expected behavior: Prepare repo_map/v1, reading_path/v1, domain_glossary/v1, risk map, and first_task_runway/v1 from observed files. - Why: The request is repo orientation before implementation. Bad example: - Prompt: codebase-onboarding 파일 안 읽고 이 레포 아키텍처를 확정해줘. - Expected behavior: Mark architecture as unobserved and inspect source evidence before making claims. - Why: Onboarding is only useful when grounded in current repo evidence. ## Completion Checklist - The plan names goals, non-goals, assumptions, acceptance criteria, and verification shape. - Draft recommendations, accepted decisions, and executor handoffs are separate states. - Rejected options or unresolved tradeoffs are recorded before handoff. ## Recovery Notes - If acceptance criteria or verification are missing, route back to clarification before h...