Skip to content

Launch checklist

One pass to run before opening steer to the wider team. Work top to bottom; each item is something you've actually exercised, not just read about. Do this in a real (or throwaway) repo, not against production work.

Pre-rollout checks

  • Plugin install tested. /plugin marketplace add element22llc/e22-plugins then /plugin install steer@e22-plugins succeeds in a clean Claude Code.
  • /steer:init tested. Runs in a fresh repo and installs the scaffold + /spec spine. (See Adopt for the existing-repo path.)
  • /steer:standards tested. Loads the always-on rules on demand — confirm it works on a hookless surface (the Desktop Chat tab / claude.ai web chat) where SessionStart doesn't fire. See Known limitations.
  • Issue creation tested. Capturing an idea creates a tracked issue through /steer:tracker-sync (MCP-first → gh fallback). Confirm gh auth status is green so the path doesn't drop to the manual floor.
  • PR workflow tested. /steer:work produces a branch + commit and opens the PR autonomously — push and gh pr create no longer pause for a human; the merge is the sole human gate. On a solo-trunk repo, the only push-time pause is the check-bash-actions.sh trunk-push gate, and only once a graduation signal stands.
  • In-CI @claude provisioned. The shipped claude.yml loads the steer plugin in CI, so it needs the ANTHROPIC_API_KEY secret. The marketplace repo is public, so the plugin clone is anonymous — no marketplace credential needed. Add the key, then @claude on a test PR and confirm the reply reflects steer standards (proves the plugin loaded). See GitHub Actions integration.
  • Docs drift CI tested. mise run docs:check passes, and a deliberate drift (e.g. add a skill without updating the reference) is caught by CI.
  • Copilot surface verified (if the team uses Copilot). Confirm .github/copilot-instructions.md, .github/prompts/, .github/instructions/*.instructions.md, .github/agents/ and .vscode/mcp.json landed, then in VS Code Copilot Chat run /steer-help and confirm the reply reflects steer standards (proves the instructions loaded — Copilot has no SessionStart hook, so that static set is its whole standards surface). Tell the team the refresh rule: those files are generated and freeze at the plugin version that bootstrapped the repo, so someone runs /steer:sync after a plugin update — it re-copies them via the copilot-surface-current capability, and /steer:sync --check reports the surface as mis-wired when it has fallen behind. /steer:init installs but stops on an already-initialized repo, so it is not the refresh path. See Copilot support.
  • One PO dry run completed. A non-developer walks the PO happy path end to end: idea → preview → hand-off for dev review. Expect a PR if the run answers that a developer will review it, and solo trunk (no PR, work on the main line) if it answers sole-contributor — both are correct endings.
  • Rollback / uninstall documented. The team knows how to back out (below).

Rollback / uninstall

To remove the plugin from a Claude Code install, use the /plugin manager (symmetric with the install steps in Installation):

/plugin uninstall steer@e22-plugins
/plugin marketplace remove element22llc/e22-plugins

This stops the hooks from firing and the rules from being injected in new sessions; it does not touch artifacts already written into a managed repo (the /spec spine, scaffold files, branches, or issues). To fully back a repo out, revert those changes through normal git history.

Next

Point new teammates at Team onboarding once these boxes are checked.