maintainlisted

# Dependency Maintenance — Stage 9 Read the detailed guide at `${CLAUDE_SKILL_ROOT}/references/maintain-detailed-guide.md` for the complete maintenance procedures, teammate spawn prompts, update strategies, and report templates. ## Context Designed to be run on a regular cadence (monthly or quarterly) to keep the codebase healthy. Outdated dependencies accumulate security vulnerabilities, miss performance improvements, and eventually create painful migration cliffs. ## Prerequisites 1. Read `CLAUDE.md` and `plancasting/tech-stack.md`. 2. Ensure `git status` shows a clean working directory. Commit or stash all uncommitted changes. 3. Check `plancasting/tech-stack.md` for the `Session Language` setting. Generate all reports in the specified language. 4. Infer package manager from lock files if CLAUDE.md Part 2 'Commands' section is empty: `bun.lockb` -> bun, `package-lock.json` -> npm, `pnpm-lock.yaml` -> pnpm. Log the inferred package manager in the report. ## Inputs - **Codebase**: Complete project directory - **Tech Stack**: `./plancasting/tech-stack.md` - **Project Rules**: `./CLAUDE.md` - **Lock file**: `package-lock.json`, `bun.lockb`, or `pnpm-lock.yaml` ## Stack Adaptation Examples use `bun` commands. Adapt to your package manager: - `npm audit` -> Bun has no built-in audit. Use `npm audit` if `package-lock.json` exists; otherwise use `bunx audit-ci` or `npx snyk test`. Document which audit tool was used in the report. - `npm update` -> `bun update` - `npm outd