← ClaudeAtlas

upgrade-projectlisted

Bring an existing leanwheel project up to the latest skills/stubs/hooks/framework. Detection-based — works even on projects scaffolded before this skill existed. Use when the user says "upgrade project", "sync leanwheel", "update scaffolding", or after pulling new leanwheel-skills changes.
rterakedis/leanwheel-skills · ★ 2 · AI & Automation · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Upgrade Project Skill **Goal:** Reconcile a project that was scaffolded by an older `leanwheel-skills` against the current version — add new assets (hooks, agents wiring, evals, metrics), refresh stubs that the project hasn't locally edited, and append any new guardrail/ doc sections — **without ever clobbering the user's own edits.** **Idempotent + non-destructive.** Adds and refreshes; never deletes project content. Always previews a plan and waits for confirmation before applying. **Relationship to `/setup`:** `/setup` is first-run scaffolding. `/upgrade-project` is the recurring sync. Existing projects have no manifest — this skill detects state by **presence and content**, then writes a manifest going forward. --- ## Step 1 — Locate the skills source Resolve `{skills_path}`: 1. `.leanwheel/manifest.json` → `skills_path` if present. 2. Else `.bmad-lite/manifest.json` (legacy — projects scaffolded before the leanwheel rename). If found, use its `skills_path` and flag the directory for migration in Step 4 (renamed to `.leanwheel/`; contents carried over unchanged). 3. Else the `add-dir` target in `.claude/settings.json` startup hook. 4. Else ask the user (e.g. `~/repos/leanwheel-skills`). Confirm `{skills_path}/.claude/skills/setup/stubs/` exists. If not, stop — wrong path. ## Step 2 — Detect surfaces Determine what this project uses (so we only sync relevant assets): - `is_apple` = `docs/setup/swift/` exists OR `.xcodeproj`/`.xcworkspace`/`Package.swift` p