vibe

Turn a rough idea into a written spec - wraps superpowers' brainstorming, applies VIBE's project heuristics, and saves the result to docs/specs/.

Generate a conventional commit message from the staged (or unstaged) changes and copy it to the clipboard.

Orchestrate a coding task - failing test contract first, numbered plan, model-tiered doers, review every diff in two passes, independent fresh-context verify

Auto-fix only the safe, mechanical issues in changed files - formatters/linters and project-local auto-fixers. Never touches security or behavior.

Fast pre-commit sanity check on changed files - a secrets scan plus the enabled overlay's quick guardians and project-local lightweight checks. Use /vibe:review for the full pass.

Mechanical-edit subagent for exact, low-judgment transformations - renames, codemods, boilerplate, lint fixes, applying a precisely described change across files. Dispatched by the conduct skill. Anything requiring a design decision goes to doer instead.

Implementation subagent for delegated, well-specified coding subtasks. Dispatched by the conduct skill with a contract (tests to pass), exact scope, and guardrails. Not for open-ended exploration or design decisions.

Code-quality review of a subtask diff. Checks craft - simplicity, idioms, conventions, no scope creep or needless abstraction - independently of whether the spec is met. Dispatched by the conduct skill in the review step, before a subtask is accepted. The second of two separate review passes; spec compliance is the other reviewer's job.

Spec-compliance review of a subtask diff. Checks that the change does exactly what its contract and the spec require - nothing missing, nothing gamed - independently of code quality. Dispatched by the conduct skill in the review step, before a subtask is accepted. The first of two separate review passes; craft is the other reviewer's job.

Security review lens for changed code. Checks secrets, injection, authn/authz, unsafe data handling, and dependency risk on a diff. Dispatched by the conduct skill when a change touches auth, input handling, endpoints, storage, or dependencies.

How to ask the user clarifying questions - always via the AskUserQuestion tool with concrete options and a recommended default. Use when a request is underspecified in ways that change the outcome.

Orchestrate a coding task end-to-end - consume the spec, write failing test contracts, plan it as numbered commit-per-task work, delegate implementation to model-tiered doer subagents, review every diff in two passes, and gate completion through an independent fresh-context verifier. Wraps the superpowers phase skills and layers model-tiering, mandatory review, and independent verification on top. Use for features, fixes, or refactors with more than a couple files of work, or whenever the user asks to orchestrate, delegate, or build something test-first.

Authoring constraints for every skill, command, and agent in this marketplace, so they run well on frontier models (Fable 5 today) and never silently fall back. Use when writing or editing any skill, command, or agent, or any orchestrator prompt that dispatches a subagent.

How model routing works across this marketplace - the PROFILE tiers, the one global Opus<->Fable switch, and the rule that no role is ever tied to a model name. Background knowledge for orchestrating, authoring agents, or switching the whole kit to a different model.