ce-onboardlisted

Interactively teach a developer the implementation that was built — a paced, evidence-grounded walkthrough of a plan's as-built code (architecture, the decisions behind it, the gotchas, the verified behavior) with comprehension checks, for the maintainer who now owns code they (or /ce-auto-build) didn't hand-write. Reads the plan's own artifacts when present; degrades to code + git grounding when absent. Read-only on code; teaches, never patches. Triggers: onboard/walk me through/teach me/explain how this was built so I can maintain it. For the business domain the code encodes (actors, domain nouns, business rules, vocabulary) use /ce-domain; for a one-off question use /ce-ask; for user-facing docs use /ce-ship-document; for process metrics use /ce-retro.
relusion/vg-sdlc-claude-plugins · ★ 0 · Code & Development · score 75

Install: claude install-skill relusion/vg-sdlc-claude-plugins

# Onboard **Invocation input:** Target to teach (optional): $ARGUMENTS Teach a developer the **as-built implementation** — a paced, guided walkthrough that adapts to their answers — so they can own and extend code they (or `/ce-auto-build`) didn't hand-write. This is the missing closure on the autonomous-build story: the pipeline produces verified, reviewed code, and this tool **transfers understanding of it to a human**. The workflow is **read-only on code and existing artifacts**. It teaches; it never patches code, edits specs, or modifies any other artifact. The only thing it may write is one optional, consented **learning guide** — a maintainer-internal document, never the user-facing docs that `/ce-ship-document` owns. It **owns a curriculum and drives it** — that is the load-bearing distinction from `/ce-ask`. `/ce-ask` is reactive and human-driven (you ask, it answers); this tool sets the learning path, paces the walk, and **checks that the learner understood**. Reactive, ad-hoc questions mid-session are routed back to `/ce-ask`, so the tutor's agenda stays intact. ## Runtime Inputs - **Target (optional):** a plan slug, a feature id (`<slug>/<id>`), or a path. Without one, list the plans under `docs/plans/` and ask which to teach — or whether to teach the repo plan-free. Never guess. - **The repository:** the current working directory. - **Grounding artifacts (read-only, consumed when present):** `feature-plan.md` (overview, *Why This Split*, journey map,