aaronsb

Start the active awareness layer. Launches attend as a persistent Monitor that surfaces environmental changes (git state, peer sessions, process activity) as notifications. Use when the user says "attend", "start awareness", "watch my session", or invokes /attend.

Check how much context window remains in this session — token budget, usage, and room left before compaction. Use when the user asks how much context/room/budget is left, or wants a context-usage gauge.

Land an increment to main through the branch → commit → push → PR → review-gate → merge → cleanup flow. The review gate is a four-square decision (review depth × human gate). Picks up wherever you are in the cycle. Use when the user says "merge this", "land this", "run a review and merge", "ship it", or invokes /merge.

Open a working session — orient to where work was left off, run a structured interview on a greenfield repo, check the context gauge to confirm it's really session-start, then recommend planning with context already warm. The opening bookend to /wrap. Use when the user says "let's start", "pick up where we left off", "what were we doing", "start a session", or invokes /start.

Carry a piece of work through the development loop — pick the loop shape (variable front, stable tail) by where the uncertainty lives, lay the tasklist, then borrow the stage skills rather than reimplementing them. Use when the user says "let's develop this", "work through this feature", "how should we approach this", "what do we do first", or invokes /develop.

Cut a versioned release — infer the version bump, update the changelog, tag, and publish artifacts (GitHub Release, package registries). The heavy sibling of /merge. Use when the user says "cut a release", "publish a release", "tag a version", "ship a release", or invokes /release.

Update the agent-ways installation to the latest version — pull the app source in $XDG_DATA, rebuild the Rust binaries (ways/attend/way-embed) and corpus, and refresh the ~/.claude projection with `ways reconcile`. Use when the user wants to update agent-ways, pull the latest ways/hooks, or refresh their ways framework install. Not for editing or authoring individual ways (that is the ways skill) or upgrading project dependencies.

Wrap up a session at a natural seam — land in-flight work, square the TaskList honestly, write a copy-paste continuation prompt, then hand off to a directed /compact. Use when the user says "wrap up", "wrap this up", "let's wrap", "end of session", "checkpoint and compact", "hand off", or invokes /wrap.

Score way matching (embedding and BM25), analyze vocabulary, and validate frontmatter. Use when testing how well a way matches prompts, checking cosine similarity or BM25 scores, inspecting the embedding engine status, or validating way files.

Check how much context window remains in this session. Use when you want to know token budget, context usage, or how much room is left before compaction. Also use proactively when working on long tasks to gauge remaining capacity.

Cite governance controls and justifications when making recommendations about code quality, security, commits, or documentation. Use when justifying why a practice matters, when a user asks "why do we do this?", when reviewing code against standards, or when recommending practices that align with NIST, OWASP, ISO, SOC 2, CIS, or IEEE controls.

Ship current work through the branch → commit → push → PR → merge → cleanup flow. Picks up wherever you are in the cycle. Use when the user says "ship it", "land this", "merge this", or invokes /ship.

Review what changed in Claude Code upstream and compare against this project's commits and ADRs. Surfaces opportunities, gaps, and ADR status drift. Discovery conversation, not compliance dashboard.

Strategy selector for structured reasoning. Lists available thinking frameworks and invokes the right one. Use when facing complex decisions, trade-offs, or when stuck.

Self-Consistency reasoning — run multiple independent reasoning paths and take consensus. Use for high-stakes decisions where reasoning errors are costly.

ReAct reasoning — explicit reason-act-observe cycle for investigation and debugging. Use when you need to interleave reasoning with tool actions systematically.