Archive one entity (opportunity, solution, objective, competitor, or persona) with a polished, contextual reason sentence. Argument: <type>/<slug> (e.g. opportunity/cold-start-context or solution/inline-viewer-pane). User context: the raw reason and kind — 'implemented: ...', 'dropped: ...', 'absorbed: ...' for opportunities/solutions; 'completed: ...', 'abandoned: ...' for objectives; 'defunct: ...', 'pivoted: ...', 'irrelevant: ...' for competitors; 'outgrown: ...', 'dropped: ...' for personas.
Challenge Me. Adversarial product challenge: a skeptical-CPO read of what you're building, who for, and the biggest strategic gap — then three direct challenges you should answer, starting with the question you're avoiding. Produces .nanopm/wiki/docs/challenges.md.
Build and maintain a ranked database of user opportunities (Teresa Torres-style — the user problems behind what you build, not the solutions). Stored as an LLM-wiki under .nanopm/wiki/entities/opportunities/: one file per opportunity + a ranked INDEX, a LOG, and an editable SCHEMA. bootstrap drafts the initial set from feedback + your assumptions + Nano's hypotheses, each marked by provenance; add captures one problem at a time. Two levels only (Theme → Opportunity); no scoring at v1 — a coarse priority instead.
Configure Supabase cloud sync for nanopm. One-time setup per machine: enter your project URL + anon key, run the migration, push your local wiki to the cloud. After setup, wiki pages sync automatically on every skill run.
Define who you're building for. Reverse-engineers personas from the codebase and prior nanopm artifacts when they exist, or builds them from scratch by interviewing you when the repo is empty. Produces the wiki Define page `.nanopm/wiki/docs/personas.md` — JTBD proto-personas plus an explicit anti-persona.
Aggregate user feedback from Dovetail, Productboard, Notion, Linear, and GitHub. Cluster into themes, surface the top unaddressed signal, map to current roadmap. Produces the wiki Feedback page (.nanopm/wiki/docs/feedback.md) — the primary input for all downstream PM skills.
Quantitative data analysis for PMs. Answers a specific product question using PostHog or Amplitude — trends, funnels, retention, paths. Writes findings to the wiki data page at .nanopm/wiki/docs/data.md, consumed by /pm-challenge-me and /pm-prd.
PM retrospective. Compares the roadmap page's NOW items against actual commits since the last roadmap run. Surfaces what shipped, what drifted, and what to carry forward. Closes the planning loop.