Stats
Actions
Tags
From vibe-workbench
Use when starting a Vibe session, planning a lane, picking the next slice, or checking repo/branch/self-plan state before edits.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vibe-workbench:vibe-orientThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Load the shared Vibe contract:
Load the shared Vibe contract:
${CLAUDE_PLUGIN_ROOT}/shared/vibe-contract.md
Current repo snapshot:
!powershell -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/vibe_repo_snapshot.ps1"
Current lane inventory:
!powershell -ExecutionPolicy Bypass -File "${CLAUDE_PLUGIN_ROOT}/scripts/vibe_lane_inventory.ps1"
Summarize the current branch, dirty state, self-plan freshness, detected assistant surfaces, and safest next work slice. Do not install tools, edit credentials, or enable hooks unless the user explicitly asks.
When the user asks about Superpowers, planning, debugging, review, or verification: invoke the relevant Superpowers skill directly (superpowers:writing-plans, superpowers:systematic-debugging, superpowers:requesting-code-review, superpowers:verification-before-completion, etc.) and save Vibe artifacts under docs/superpowers/{plans,specs,research}/ per the shared contract.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub lutherfourie/vibe --plugin vibe-workbench