adoptlisted

Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
NITISH-R-G/skills-i-use · ★ 1 · AI & Automation · score 68

Install: claude install-skill NITISH-R-G/skills-i-use

# Adopt — Brownfield Template Adoption This skill audits an existing project's artifacts for **format compliance** with the template's skill pipeline, then produces a prioritised migration plan. **This is not `/project-stage-detect`.** `/project-stage-detect` answers: *what exists?* `/adopt` answers: *will what exists actually work with the template's skills?* A project can have GDDs, ADRs, and stories — and every format-sensitive skill will still fail silently or produce wrong results if those artifacts are in the wrong internal format. **Output:** `docs/adoption-plan-[date].md` — a persistent, checkable migration plan. **Argument modes:** **Audit mode:** `$ARGUMENTS[0]` (blank = `full`) - **No argument / `full`**: Complete audit — all artifact types - **`gdds`**: GDD format compliance only - **`adrs`**: ADR format compliance only - **`stories`**: Story format compliance only - **`infra`**: Infrastructure artifact gaps only (registry, manifest, sprint-status, stage.txt) --- ## Phase 1: Detect Project State Emit one line before reading: `"Scanning project artifacts..."` — this confirms the skill is running during the silent read phase. Then read silently before presenting anything else. ### Existence check - `production/stage.txt` — if present, read it (authoritative phase) - `design/gdd/game-concept.md` — concept exists? - `design/gdd/systems-index.md` — systems index exists? - Count GDD files: `design/gdd/*.md` (excluding game-concept.md and systems-index.md) -