plan-tune

When to invoke

Use when asked to "tune questions", "stop asking me that", "too many questions", "show my profile", "what questions have I been asked", "show my vibe", "developer profile", or "turn off question tuning".

Proactively suggest when the user says the same vibestack question has come up before, or when they explicitly override a recommendation for the Nth time.

Preamble

eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown"
_LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
  _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
  echo "LEARNINGS: $_LEARN_COUNT entries loaded"
  if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
    ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true
  fi
else
  echo "LEARNINGS: none yet"
fi

{{include lib/snippets/session-host.md}}

{{include lib/snippets/decision-brief.md}}

{{include lib/snippets/working-protocols.md}}

{{include lib/snippets/state-protocols.md}}

Step 0: Detect what the user wants

Before routing on intent, check two implicit gates — they fire first:

• Consent gate. If question_tuning is not true AND ${VIBESTACK_HOME:-$HOME/.vibestack}/.question-tuning-prompted does not exist → run Enable + setup. The marker is written whichever way the user answers (even a decline), so someone who said "not now" is never re-prompted on later invocations.
• Setup gate. If question_tuning is true AND developer-profile.json's declared object is empty AND ${VIBESTACK_HOME:-$HOME/.vibestack}/.declared-setup-prompted does not exist → run the 5-question declaration (the Q1–Q5 block under Enable + setup), then write that marker. This backfills the declared profile for anyone who enabled tuning directly (route 8 below) without the wizard.

Guard both marker reads with [ -f … ], per the ~/.vibestack/ session-state convention.

If neither gate fires, route on plain-English intent (not keywords):