# Vibe How Do We Do

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

- Skill: `majiayu000/vibe-how-do-we-do` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/vibe-how-do-we-do`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/vibe-how-do-we-do/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/vibe-how-do-we-do

---


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