Menu
Load the always-on operating manual on demand. In Claude Code the rules are already injected, so this only repeats them.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Scaffold an autonomous loop for a managed repo — a scheduled GitHub Actions workflow that wakes on its own, triages work (CI failures, open issues, drift) via /steer:audit + /steer:next, drafts fixes in isolated worktrees reviewed by steer-reviewer, and opens draft PRs. Wired to stop at every human gate (rule 53): it delivers up to the PR, it never merges/deploys. Instantiates templates/github/workflows/steer-loop.yml and lands it via the normal autonomous branch-push + PR (Commit autonomy — the merge review is the gate).
Adopt an existing repo that never went through bootstrap (a "vibe-coded" app) into the standards — reverse-engineer the /spec from the code, triage productionization (Keep/Refactor/Rewrite/Reject per area), and sync the plugin's bundled scaffolding without clobbering working code.
Guided flow for a non-technical product owner — idea → interview → approved spec → working local app → handoff for dev review, with Claude driving all tooling.
One-time setup for a new managed repo — bootstrap the /spec spine + repo scaffolding from the plugin's bundled scaffold (the plugin replaces the old static repository-template as the bootstrap source), or resolve placeholders in a legacy template fork. In both cases pin the toolchain and leave the repo working spec-first.
Absorb a PO-supplied spec/roadmap document (docx/pptx/xlsx/pdf) into the /spec spine — version-stamp and commit the binary plus a normalized Markdown extraction under spec/sources/ — relocating the dropped file into that canonical home so it does not linger where it was uploaded — git-diff it against the prior version, and surface a structured what-changed report. Then route the real changes into intent/contract/vision/roadmap and the tracker via the relevant skills, never clobbering human-authored prose (conflicts become Open questions). Idempotent on an unchanged document. In clarify mode, absorbs a client clarification document instead: it segments the extraction, maps each unit against open questions and the feature list, and sorts them into a three-bucket worklist — answers routed to /steer:questions, new scope to the reconcile rows, unmatched surfaced for the human.
Make GitHub branch protection — the real gate against direct-push-to-main — reliable on a managed repo: read policy/branch-protection.yml, diff it against the repo's live protection, and on explicit confirmation apply the missing settings via gh api (branch protection, secret scanning, Dependabot alerts). Verify by default; configures the GitHub-side gate only — steer is advisory in the local session (rule 95) and cannot block local pushes.
Based on SOC occupation classification
| name | standards |
| description | Load the always-on operating manual on demand. In Claude Code the rules are already injected, so this only repeats them. |
| when_to_use | Use at the start of a session on any surface where the SessionStart hook does NOT auto-inject the rules — notably the Claude desktop/web Chat tab and chat-only surfaces, where plugin hooks do not run. |
| disallowed-tools | Edit, Write, NotebookEdit, EnterWorktree |
The standards are normally injected once per session by the steer
SessionStart hook. That hook does not fire on the Claude Desktop Chat tab or
claude.ai web chat — those surfaces install plugins (so skills and MCP work) but
do not run hooks, so a session there starts with none of the org rules in
context. Run this skill first on those surfaces. (On Claude Code — the CLI, the
IDE extensions, and the Desktop Code tab — and in Cowork, the hook injects the
rules automatically and you don't need this skill.)
Do this now:
Read every rule file, in lexical (numeric-prefix) order, from:
${CLAUDE_PLUGIN_ROOT}/rules/
The files concatenate, in that order, to form the full operating manual.
Adopt their contents as your standing operating rules for the rest of this session — the same status they would have if they had been injected at startup. They override generic defaults and remain in force for every subsequent turn.
Give the user a one-line confirmation naming the plugin version (read it from
${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json) — e.g. "Standards
vX.Y.Z loaded." Do not dump the full ruleset back to the user;
just confirm and proceed.
The router (00-router.md) points to the on-demand reference skills
(/steer:reference [conventions|traceability|design-sources|context-hygiene|architecture-diagrams], /steer:init,
/steer:adopt) — those work normally on the Chat tab and web chat since skills
are supported there; only the always-on injection needed this fallback.
