project-onboardinglisted

Runs a project activation sequence. Fires on "new project", "project activated", "onboard this project", "set up the project", or when a project first gets its workspace folder. One short guided intake, then automated setup - folders, deploy model, credential references, repo, branches, status docs - so project starts cost near-zero thought.
Shaisolaris/solaris-dev-shop · ★ 1 · AI & Automation · score 67

Install: claude install-skill Shaisolaris/solaris-dev-shop

# Project Onboarding This employee activates a new project into the workspace. Ask ONLY the short intake below (plain chat, never MCQ widgets), then set up everything. ## Step 0 - Read the local project doctrine first If the workspace has a project doctrine file (e.g. `project/FLEET.md`, `project/DOCTRINE.md`, or a company-facts reference), read it before the intake. Skipping a present doctrine = gate failure. ## The intake (30 seconds, defaults in brackets - silence accepts defaults) 1. Project type? web app / website / mobile app / desktop app / game / other 2. Deploy model? [web: main=live, dev=staging | mobile/desktop/game: nothing auto-deploys; main=release-candidate; store/installer submission = human-approved step | none] 3. Project/client name + which credentials exist or are needed (hosting, domain, stores, DBs, APIs)? 4. Budget/timeline anchors worth recording? ## Automated setup (execute ALL, verify each with real output) 1. FOLDERS: `<project-root>/` with exactly `Scope/`, `Development/`, `Delivery/`, `Assets/` + `STATUS.md` carrying: the project brief, DEPLOY-MODEL line (from intake), stage, and client/commercial terms if any. 2. CREDENTIALS: create or update the project's credential reference sheet (one row per credential from intake: system, username, where-the-secret-lives). NEVER store secret values in the sheet or chat - reference keychain/secret-manager locations. Confirm row count written. 3. REPO (if code project): create/verify the git repo, create a