pm-solutions

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, Confirm, Choose.
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: [].

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
_OPP_DIR=".nanopm/wiki/entities/opportunities"
_SOL_DIR=".nanopm/wiki/entities/solutions"
mkdir -p "$_SOL_DIR"

What this skill does

/pm-solutions <opportunity-slug> is the Solutions node of the Opportunity Solution Tree (Outcome → Opportunity → Solution → Assumption). nanopm already produces Outcomes (objectives) and Opportunities (the DB), but nothing bridged an opportunity to a compared set of candidate solutions — so the founder picked the first idea in his head and jumped straight to /pm-prd. This skill fills that gap: it convenes a panel of three fixed expert lenses (Eng / Design / Business), makes them propose competing solutions in parallel, then converges them into a comparison the founder can weigh.

The shape is the same recipe each run, built on the three wiki primitives — query → reasoning → ingest (no bespoke read logic), with lint keeping it honest after the fact:

• RESOLVE — resolve the opportunity slug to one file (or list candidates and stop).
• QUERY (read primitive) — one nanopm_query_prompt subagent reads the wiki and returns a cited, lens-relevant grounding for the panel (the persona's JTBD, the objectives / strategy / bet, the product surface + structural constraints) — the same query op every other skill uses, instead of leaning on the preamble briefs alone.
• DIVERGE (reasoning primitive) — three lens-subagents (Eng / Design / Business) dispatched concurrently in one turn, each grounded in the opportunity file + the cited QUERY digest.
• CONVERGE — one pass that dedups overlapping proposals and emits ≥3 solutions, each with the full field set; the converged comparison table is canonical, but every row keeps its lens tag and a one-line dissent note — the room stays visible.
• WRITE — one wiki/entities/solutions/<slug>.md per solution via the ingest apply primitive, regenerate INDEX.md, append a bidirectional pointer block to the parent opportunity page.
• CHOOSE — present the comparison; the founder shortlists, then marks one chosen. The agent never auto-chooses.