Skill v1.0.0

version: "1.0.0" name: discuss description: Think something through with VBW before building (a decision, an idea, a concern): plain questions, trade-offs, a recommendation, and the outcome recorded. argument-hint: "[what to think through]" allowed-tools: Bash("${CLAUDE_PLUGIN_ROOT}/bin/vbw" ) Bash(vbw )

"${CLAUDE_PLUGIN_ROOT}/bin/vbw" status 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" show decisions 2>&1 || true
"${CLAUDE_PLUGIN_ROOT}/bin/vbw" interview 2>&1 || true

Write to the user's level, explanation depth and involvement (above; "-": plain words).

The user wants to think this through: $ARGUMENTS

If that is empty, ask what is on their mind, offering starting points that fit the project's state.

Help them decide well, not for them. Bring up what they haven't considered when it matters: cost, where data lives, security, maintenance effort, what is hard to change later.

1. Understand first: read what you need (.vbw/spec.md, .vbw/map.md, the

code) and say back in a sentence what you understood.

1. Ask one question at a time (AskUserQuestion): recommendation first,

marked "(Recommended)", a trade-off per option. Ask only what changes the outcome.

1. Record the outcome, and say what you recorded:

• each decision: vbw decide "<what was decided>" "<why>";
• a new or changed requirement: vbw spec add auto|human "<statement>", or

edit .vbw/spec.md and run vbw spec sync; say that the plan's contract will need approval again;

• an idea for later: vbw todo add "<idea>".

1. Close with what was decided; /vbw:vibe continues from it.

Outside a VBW project (the status above says so), discuss all the same, and offer /vbw:init at the end so the decisions can be kept.