description: Alias for /ground — the demand-evidence gate on the build decision. Binds every product bet to real demand evidence (revealed-&-costly > specific-stated > vanity proxy) and REFUSES to license a build on anything weaker than specific stated demand: defaults to UNKNOWN/PUSH and ships the cheapest test that would settle it. Stops craft drifting into impressive-but-unwanted. Modes: <bet|product> (extract + falsify + verdict) | audit | apply. argument-hint: "<the product bet / feature / product to ground in demand> | audit | apply (default: extract + falsify + verdict)" allowed-tools: Read, Edit, Write, Bash
Alias for /ground. Follow the ground skill (ground/SKILL.md) exactly — same modes (<bet|product> | audit | apply), same evidence-hierarchy refusal criterion (PULL ≥ Tier-1, vanity caps at UNKNOWN, cite-or-declare-UNKNOWN), same falsification + founder-bias guard, same gates-and-grades enforcement (verdict gates ship via /redline; each bet emits a falsifiable demand-prediction to your prediction ledger), same propose-on-approval + PUSH-caught/prediction-hit-rate metric.
Why two names: ground is the self-documenting verb — keep the product grounded in real demand, do not float on proxy and conviction (a cold reader infers the method). pmf is the recognizable term for the goal it serves (product-market fit). Use whichever reads truer; they run the identical procedure.