← ClaudeAtlas

speccraft.onboardlisted

Onboard an existing (brownfield) application by discovering its architecture from code. Use when user runs $speccraft.onboard or asks to onboard/import an existing codebase into this workflow.
RishabhSoftwarePrivateLimited/spec-craft · ★ 0 · AI & Automation · score 68
Install: claude install-skill RishabhSoftwarePrivateLimited/spec-craft
Read `spec/commands/speccraft.onboard.md`, `spec/AGENTS.md`, and `spec/architecture/README.md` in full, then onboard the existing application described by the input. Input: read the optional path to existing code the user supplied after invoking this skill (only needed if it isn't already inside `src-code-frontend/`/`src-code-backend/`). Rules before starting: - confirm `spec/architecture/ARCH-DECISIONS.md` does not already have real `AD-FRONTEND-*`/`AD-BACKEND-*` content — if it does, stop and report; this command does not re-sync an already-populated file - ask Layer Scope interactively in chat (`frontend` / `backend` / `both`) — never infer it from which code root exists or from scan results - for each confirmed layer, locate its existing code (`src-code-frontend/`/`src-code-backend/` first, else the provided path) — never assume a path - scan and split findings into Tier 1 (LLD-required stack decisions only — the enumerated `AD-FRONTEND-*`/`AD-BACKEND-*`/`AD-X-*` set) and Tier 2 (everything else — `rules/`/`skills/` content), each with file:line evidence - present both tiers together for review; only write on `approved` — respond `approved` / `revise: [reason]` / `blocked: [reason]` - write Tier 2 to whichever root the code actually lives in (`src-code-frontend/`/`src-code-backend/` if already there, else the provided path) — never move or relocate existing code - report the minimal handoff block from `spec/commands/speccraft.onboard.md`, then STOP — do not chain into `