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 (Cowork/desktop) 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 a PR, and the push/PR gate correctly pauses for a human.
  • [ ] In-CI @claude provisioned. The shipped claude.yml loads the steer plugin in CI, so it needs the ANTHROPIC_API_KEY secret and the shared marketplace GitHub App (STEER_APP_ID / STEER_APP_PRIVATE_KEY, set once at the org level). Create the App, 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.
  • [ ] One PO dry run completed. A non-developer walks the PO happy path end to end: idea → preview → PR for dev review.
  • [ ] 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.