pm-retro

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

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
_RETRO_FILE="$(nanopm_wiki_doc_path "retro-$(date +%F)")"

Phase 0: Prior context

source ~/.nanopm/lib/nanopm.sh 2>/dev/null || source .nanopm/lib/nanopm.sh 2>/dev/null || true
nanopm_context_read pm-retro

If prior retro found: "Prior retro from {ts}. This run covers commits since then."

Phase 0.5: Surface objectives and carry-forward items

Pull the specific OKRs and open opportunities before the full query — so the retro compares commits against measurable key results, not just broad plan summaries:

source ~/.nanopm/lib/nanopm.sh 2>/dev/null || source .nanopm/lib/nanopm.sh 2>/dev/null || true
nanopm_wiki_search "objective key result okr goal" objective 5

source ~/.nanopm/lib/nanopm.sh 2>/dev/null || source .nanopm/lib/nanopm.sh 2>/dev/null || true
nanopm_wiki_search "roadmap carry-forward shipped" doc 3

For each result, Read the full page (path column). Hold the specific KRs — use them in Phase 4 to check whether commits moved any measurable needle, not just whether they loosely map to a roadmap label.

Phase 1: Context assembly (query the wiki) + git repo check

The retro compares the planned work (the roadmap) against the actual work (git history). Pull the planned side through the query primitive — one read-side call that synthesizes the roadmap's current items, instead of reading the page directly (the recipe pattern). You reason over the cited synthesis the query returns. Print the prompt and dispatch it with the Agent tool (one subagent); on a host with no Agent tool, follow its steps inline.