Set up a devroot

A devroot is a workspace repository that agent sessions run from: a few scripts, an AGENTS.md that says how to work, and the skills under its agent directories, with project checkouts, dotfiles and a vault beside them. This skill makes one. The mechanics live in this skill's scripts/setup-devroot; read its --help first.

Check the GitHub CLI first: gh auth status. Without gh, or signed out, stop and give the install and gh auth login steps; the template is fetched through it, and the scripts in the workspace use it.
Ask where the devroot should go, suggesting ~/devroot, and let the user rename it. The directory must be new or empty. Confirm the path.
Ask for the GitHub user whose dotfiles and vault repositories the workspace brings in, suggesting the login from gh api user --jq .login. A user with neither repository still names themselves; setup notes what is missing and leaves it for later.
Run the script with --dry-run, the path and --user, and report what it will do. Then run it for real. It fetches devroot-template-latest/ fresh from huntie/huntiestack, installs every skill from huntie/skills into the agent directories, writes the initial commit, and runs the workspace's own scripts/setup. Exit 3 means setup could not clone a dotfiles or vault repository, expected for a new user; say which.
Ask whether to set up a vault now, the private repository of plans and working knowledge the workspace reads. On yes, change into the new devroot and follow the setup-vault skill. Otherwise say it can be done later with /setup-vault from inside the workspace.

End with the path, the skills installed, what setup skipped, and AGENTS.md as the next thing to read for how sessions work there.