Markdown-native PMF / founder-research tracker. Daily interview-driven logs, a hypothesis/evidence ledger, weekly reviews, a generated index, and a one-time importer — with non-negotiable no-fabrication rules. Commands: /pmf-start, /pmf-wrap, /pmf-review, /pmf-index, /pmf-import.
One-time import of an existing HTML/JSON PMF tracker (a pmf-data.json export) into the Markdown tracker layout — preserving the overview, thesis, scratchpad, every hypothesis, and weekly reviews verbatim. Use when migrating from a prior tracker, or when the user says 'pmf import', 'import my pmf data', 'migrate the tracker', 'convert pmf-data.json', or types '/pmf-import'.
Regenerate the tracker's INDEX.md from the current Markdown files — a status table of all hypotheses, grouping by area, the reviews list, and a 'findings so far' section (validated hypotheses only). Deterministic and idempotent. Use when the user says 'pmf index', 'rebuild the index', 'refresh the pmf index', 'regenerate INDEX.md', or types '/pmf-index'.
Roll up the week's daily PMF logs into a Weekly Review entry (Focus / Learned / Decisions / Next), surface recommended hypothesis signal/status updates for you to confirm, and refresh the index. Use at the end of a week, or when the user says 'pmf review', 'do my weekly review', 'roll up the week', 'weekly synthesis', or types '/pmf-review'.
Start a daily PMF / founder-research session. Resumes recent state (yesterday's log, open hypotheses, the last weekly review), interviews the founder about what they did, learned, heard from customers, and which hypotheses moved, then writes today's daily log as structured Markdown. Use at the start of a working day or when the user says 'pmf start', 'start my pmf day', 'log my research day', 'daily check-in for the venture', or types '/pmf-start'.
End-of-day PMF wrap-up. Summarizes the day from today's log, updates the hypotheses it touched (status / signal / evidence — only with explicit confirmation), captures decisions, and appends a dated thesis revision if direction changed. Use at the end of a working day or when the user says 'pmf wrap', 'wrap up my pmf day', 'close out the day', 'update my hypotheses', or types '/pmf-wrap'.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimnpx claudepluginhub dennisonbertram/pmf-tracker-cc --plugin pmf-tracker-ccBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Markdown-native PMF / founder-research tracker for Claude Code.
Instead of a SaaS dashboard, your product-market-fit process lives as structured, indexed Markdown
inside a repo you own. You drive it conversationally: each day you run /pmf-start, Claude resumes
where you left off, interviews you about what happened, and writes it down — honestly. No invented
numbers, no inflated metrics, evidence weighted and sourced.
The frame is a founder's customer-discovery loop:
area · signal · status · evidence_weight · sources and the
classic Hypothesis / Evidence / Experiment / Result structure.Focus / Learned / Decisions / Next, rolled up from the week's logs.INDEX.md — status table, grouping by area, reviews, and a "findings so far" section
that only ever lists validated hypotheses.Everything is plain Markdown with YAML front-matter, so it diffs in git, renders anywhere, and is yours.
| Command | What it does |
|---|---|
/pmf-start | Begin a daily session: resume recent state, interview you, write today's daily log. |
/pmf-wrap | End-of-day: summarize, update the hypotheses the day touched (status changes require your confirmation), capture decisions. |
/pmf-review | Roll up the week's logs into a weekly review and refresh the index. |
/pmf-index | Regenerate INDEX.md deterministically from the current files. |
/pmf-import | One-time import of an existing pmf-data.json tracker into the Markdown layout. |
This tracker is a working reference, not a pitch. The rules in
references/honesty-rules.md are non-negotiable and every command obeys them:
TBD, never a placeholder number.✅ ≥2 independent sources · ⚠️ partial · 🔵 single-source/n=1 · ❌ refuted./plugin marketplace add dennisonbertram/pmf-tracker-cc
/plugin install pmf-tracker-cc
Then, in any repo where you want to track a venture:
/pmf-start
On first run it offers to start empty (a clean pmf/ scaffold) or to copy the fictional Acme Inbox
sample so you can see a populated tracker. When you're ready for your own venture, /pmf-start detects the
sample and offers to clear it. It also offers to gitignore your private scratchpad.
To run it from a local checkout (e.g. while developing):
/plugin marketplace add /absolute/path/to/this/repo
/plugin install pmf-tracker-cc
The tracker root is resolved from the current working directory (git rev-parse --show-toplevel →
pmf/), so /pmf-start writes into whatever repo you're in — independent of where the plugin is installed.
If you already track PMF in an HTML/JSON tool that exports a pmf-data.json:
/pmf-import --data /path/to/pmf-data.json
It runs a dry run, asks you to confirm, imports safely (never overwrites existing files), then verifies
the round-trip is verbatim. Fields with no source in the original data (evidence_weight, sources,
created/updated) are added with an explicit "auto-inferred on import — verify" marker.
.claude-plugin/ plugin.json + marketplace.json (manifest)
skills/ the five /pmf-* commands (one SKILL.md each)
workflows/ pmf-review.js — the typed, parallel weekly rollup
references/ the single source of truth (format spec, honesty rules, evidence vocab, importer contract)
templates/ literal Markdown skeletons the commands instantiate
examples/ a fictional sample tracker (Acme Inbox) — explore it, then clear it to start your own
scripts/ pmf_import.py (import + --verify), pmf_index.py (deterministic INDEX), pmf_md.py (shared helpers)
The scripts are pure Python stdlib — no network, no pip. references/format-spec.md is canonical: if a
command and the spec disagree, the spec wins.
MIT © 2026 pmf-tracker-cc authors
A structured orchestration system for Claude Code that plans, delegates, reviews, and learns. Includes coordinator, worker, and reviewer agents.
UX testing toolkit for Claude Code — generate user journey stories, walk them through a real browser, and implement the issues found.
Comprehensive macOS health, security, and performance monitoring — beautiful daily HTML reports, cron automation, and one-command diagnostics.
Complete development toolkit — UX testing, multi-agent coordination, TDD workflow, GitHub templates, research spikes, and repo scaffolding. Works with Claude Code.
Create and edit Obsidian vault files including Markdown, Bases, and Canvas. Use when working with .md, .base, or .canvas files in an Obsidian vault.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Frontend design skill for UI/UX implementation
Memory compression system for Claude Code - persist context across sessions
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, ad creative, and growth