Make a project Lean Context Development aware. Use when a project has no .claude/rules/lcd-conventions.md yet (first-time LCD setup), when the user says "set up LCD here" / "make this project LCD-aware" / runs /lcd:onboard, or to refresh a stale MAP or conventions block. Generates a MAP.md of the actual code organization, seeds DECISIONS.md, records test-discovery/runner conventions, asks once where LCD artifacts live, and appends a triage pointer to CLAUDE.md. Works on new and existing projects. Retrofit-safe.
Ground a LCD work-item in CURRENT best practice before deciding on an approach. Resolves up-to-date library/API/tooling guidance via Context7 and a targeted web search, in a subagent, and returns a few dated bullets. Use at the start of Standard/Deep work that touches a library, framework, SDK, API, or pattern whose current best practice you're not certain of — before writing the plan or choosing a dependency.
Fold a closed LCD work-item's acceptance criteria into the project's living current-state spec (SPEC.md) at closeout. Runs only when `living-spec: on` in lcd-conventions. Use at a work-item's finish line — after audit PASS (Deep) or when the JOURNAL flips to done (Standard) — to compact the frozen delta into the one document that says "what the system does now". Not for mid-work edits (that's lcd:refine).
Autonomous build verb of LCD. Use when an LCD work-item (docs/lcd/work/<slug>/ or the conventions artifact-root) has failing tests to drive to green — after Deep-lane test-gen, or once a Standard-lane JOURNAL's STEPS reach failing tests. Iterates the test runner with bail, fixes the first failing test with minimum code, commits, repeats until green. Hard iteration cap and stuck escalation.
Autonomously correct a LCD work-item's plan when reality drifts from it — a STEP/task that's now wrong, a task that needs splitting, a MAP zone/invariant that no longer matches the code, or stale knowledge. Updates the artifact AND logs the change without waiting to be asked. Use mid-work when you notice the recorded plan no longer matches what the work actually needs.
Lean Context Development triage. Use when starting non-trivial new work in any LCD-onboarded project — a new feature, a multi-file change, a refactor that alters architecture, or anything you'd want a fresh session to pick up cold. Scores the work, picks a lane (Quick / Standard / Deep), states it in one line, and routes. Not for typo fixes, single-line edits, dependency bumps, formatting, or a bug fix whose cause is already known.