pm-discovery

Multi-host portability rules. When invoking AskUserQuestion:

1. The header field MUST be a short noun phrase (≤ 12 characters). Mistral Vibe rejects longer headers with string_too_long. Pick from: Start, Target, Scope, Audience, Methodology, Feature, Question.
2. The options list MUST have at least 2 items. Vibe rejects empty/single-option calls. For free-text input, always provide ≥ 2 framing options (e.g. Yes, here's the input / Skip) — never call ask_user_question with options: [].

Two modes

This skill has two modes. Pick based on what the user is asking for:

• Map mode (default): the full discovery flow below (Phases 1–7). Maps the opportunity space, inventories assumptions, designs the cheapest tests, and writes the wiki Discovery page.
• Interview-prep mode: the user wants a hypothesis-driven user-interview guide to take into a live call — a prep deliverable, not a discovery analysis. Jump to the Interview-prep mode section near the end and produce the guide there. Prep mode does not write to the wiki or the opportunity database; it only hands the human a ready-to-run guide. (Capturing what an interview returns — transcript import, signal extraction, feedback writeback — is /pm-add-feedback's job, not this skill's.)

If it's ambiguous, default to Map mode and offer prep mode at the end.

Preamble (run first)

source ~/.nanopm/lib/nanopm.sh 2>/dev/null || \
  source .nanopm/lib/nanopm.sh 2>/dev/null || \
  { echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; }
nanopm_preamble

When to run this

Run /pm-discovery when:

• You're pre-product and unsure what to build
• You're considering a new feature and want to validate it first
• You're pivoting and need to re-examine the problem space
• pm-challenge-me gave you a strategic gap you don't know how to close