init-workoslisted

Initialize a WorkOS-style workspace on top of an existing directory that already has files organized by project. Use whenever the user says 'init workos,' 'set up workos here,' 'initialize my workspace,' 'bootstrap workos,' 'scaffold workos,' 'convert this to workos,' or asks to lay the WorkOS structure over a folder they already use. Recursively scans the existing directory to detect domains (top-level areas of work) and projects (individual engagements / efforts), including projects nested one level deep inside groups (folders like `clients/` that bundle related projects together). Creates root CLAUDE.md (with routing map), MEMORY.md, ARCHIVE.md, plus per-domain CLAUDE.md + MEMORY.md and per-project CLAUDE.md + MEMORY.md. Groups themselves are not scaffolded — they're just folder containers; the domain routing map handles routing into grouped projects using full relative paths. Never moves or modifies existing files without explicit approval. Narrates each step so the user understands what's being created a
dylanmoo/workos-plugin · ★ 0 · Data & Documents · score 70

Install: claude install-skill dylanmoo/workos-plugin

# Init WorkOS A one-time bootstrap skill that lays a WorkOS scaffold over an existing project-organized directory. Run once per workspace; afterward use `/create-project`, `/session-audit`, and `/workspace-audit` for ongoing maintenance. ## Narration — explain as you go This skill writes files into the user's workspace. **Tell the user what you're doing and why at every step.** Each Step below has a "Narrate:" line — that's the message to send before performing the step. Don't be silent between actions. Treat the user as a smart collaborator who wants to understand the moves you're making with their files. Default tone: brief, plain-spoken, one or two sentences per checkpoint. State the action and the reason. Example: "Scanning your folders to figure out what's a domain, a project, and what's just storage. Won't write anything yet." Not example: "Initiating recursive directory traversal at depth 3." ## What this skill does 1. **Recursively detects** the existing folder shape — which top-level folders are domains, which subfolders are projects (individual engagements), which folders are group containers that bundle multiple projects together, and which are content storage. 2. **Creates** files at three levels: root, domain, and project. Groups are detected but **not** scaffolded — they're pure folder containers; the domain's routing map handles routing into grouped projects via full relative paths (e.g., `clients/acme/`). 3. **Wires the routing maps** at root and domain