# spw.quest — initialize a mounted Spw workbench Agent entrypoint: https://spw.quest/init ## Models Each command asks the model to fetch this page and run the setup in the current repository. Claude Code: claude -p 'Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.' Codex: codex exec 'Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.' Grok: grok 'Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit.' Cursor, Gemini, or another agent: paste the job below into the agent chat. Read https://spw.quest/init and initialize .spw/_workbench in this repository. Verify with doctor. Stop before any commit. ## Shell test -d .git || git init git submodule add https://github.com/spwashi/spw-workbench .spw/_workbench git -C .spw/_workbench checkout 3eaab637767222ffe248449da7262a251c4c608b npm --prefix .spw/_workbench ci --ignore-scripts npm --prefix .spw/_workbench run spw:init -- ../.. npm --prefix .spw/_workbench run spw:doctor -- ../.. git diff --check ## Git, in this order https://spw.quest/git.txt https://spw.quest/git.md test -d .git || git init git submodule add https://github.com/spwashi/spw-workbench .spw/_workbench git -C .spw/_workbench checkout 3eaab637767222ffe248449da7262a251c4c608b git submodule update --init -- .spw/_workbench git diff --check Initialize the current repository with Spw Workbench at .spw/_workbench. Read this entire recipe before editing. Follow the target repository's existing instructions. The section "Git, in this order" is the only git procedure. Use the one command that matches the folder you have. Spw supplies language, parser, CLI, and editor tooling. The consumer owns .spw/; the mounted workbench owns .spw/_workbench. Keep this repository's own instructions, framework, and identity. 1. Inspect the working directory, git status, existing instructions, .gitmodules, .spw/, and git config core.hooksPath. Preserve unrelated changes and existing files. Require Git and Node ^20.19.0 || >=22.12.0. Confirm this directory is the intended consumer root. 2. Follow "Git, in this order" for the repository, the submodule link, the reviewed revision, and the download. Verify the workbench origin and read its own quick start. 3. Review the mounted package.json and lockfile, then install its locked tooling dependencies when the consumer's dependency policy allows: npm --prefix .spw/_workbench ci --ignore-scripts Leave the consumer's own dependency graph alone. 4. From the consumer root, run: npm --prefix .spw/_workbench run spw:init -- ../.. The ../.. target is relative to npm's mounted package working directory. Init seeds consumer files and leaves existing scaffold files in place. It may install a commit-review workflow and .git/hooks/pre-commit. Read the existing hook first. Report when core.hooksPath means that hook will not run. 5. Read .spw/README.md, .spw/index.spw, .spw/workspace.spw, and .spw/mount.spw. Run: npm --prefix .spw/_workbench run spw:doctor -- ../.. npm --prefix .spw/_workbench run spw -- roots npm --prefix .spw/_workbench run spw -- tree @spw --depth 3 git diff --check Default consumer scans exclude _workbench. Leave the workbench grammar in place. 6. Report the mount revision, created and skipped files, hook changes, doctor result, and any blocked step. Run the checks before you call the setup done. Stop before any commit, push, or deploy. Expected core files: .spw/README.md, .spw/index.spw, .spw/mount.spw, .spw/workspace.spw, plus .agents/workflows/commit-review.md. The pinned initializer may seed additional authored surfaces; inspect its output and report those names. Source: https://github.com/spwashi/spw-workbench/blob/3eaab637767222ffe248449da7262a251c4c608b/docs/runtime/md/quick-start.md Ownership: https://github.com/spwashi/spw-workbench/blob/3eaab637767222ffe248449da7262a251c4c608b/docs/runtime/md/mounted-workbench.md