Vibe-Skills vibe-what-do-i-want

Clarify intent and freeze requirements by entering the canonical vibe runtime with a discovery-first bounded stop.

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-what-do-i-want" ~/.claude/skills/foryourhealth111-pixel-vibe-skills-vibe-what-do-i-want && rm -rf "$T"

manifest: bundled/skills/vibe-what-do-i-want/SKILL.md

tags

#requirement-gathering #intent-clarification #discovery #structured-interview #vibe-runtime

source content

Use canonical

vibe

as the only governed runtime authority for this request.

Entry bias:

clarify what the user actually wants
shape scope before solutioning
strengthen requirement-first discovery
stop after canonical
```
requirement_doc
```

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
```
xl_plan
```
,
```
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:

stronger
```
deep_interview
```
stronger requirement clarification before planning
a bounded terminal stage of
```
requirement_doc
```

Request: $ARGUMENTS