Vibe-Skills vibe-how-do-we-do

Design the approach and execution plan by entering the canonical vibe runtime with a planning-first bias.

install
source · Clone the upstream repo
git clone https://github.com/foryourhealth111-pixel/Vibe-Skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/foryourhealth111-pixel/Vibe-Skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/bundled/skills/vibe-how-do-we-do" ~/.claude/skills/foryourhealth111-pixel-vibe-skills-vibe-how-do-we-do && rm -rf "$T"
manifest: bundled/skills/vibe-how-do-we-do/SKILL.md
source content

Use canonical

vibe
as the only governed runtime authority for this request.

Entry bias:

  • choose an approach
  • design execution structure
  • sequence the work before implementation
  • stop after canonical
    xl_plan

Execution rules:

  • delegate to canonical
    vibe
  • keep
    vibe
    as the only runtime authority
  • do not create a second requirement surface
  • do not create a second plan surface
  • do not create a parallel runtime
  • do not continue into
    plan_execute
    or
    phase_cleanup
    unless the user explicitly re-enters through canonical
    vibe
    or another approved wrapper

When this wrapper is chosen, enter canonical

vibe
with:

  • approach selection
  • explicit planning
  • stronger transition into
    xl_plan
  • a bounded terminal stage of
    xl_plan

Request: $ARGUMENTS