Skip to main content

/jaan-to:detect-product

Product reality extraction with evidence-backed features, monetization, and metrics.


What It Does

Extracts the "product reality" from the repository using a 3-layer evidence model: surface (routes/screens), copy (user-facing text), and code path (business logic). Scans for features, value proposition signals, monetization/billing, entitlement enforcement, analytics instrumentation, feature flags, and technical/business constraints.


Usage

/jaan-to:detect-product
ArgumentRequiredDescription
repoNoTarget repository (defaults to current)

Output

FileContent
docs/current/product/overview.mdProduct overview with feature summary
docs/current/product/features.mdFeature inventory with 3-layer evidence
docs/current/product/value-prop.mdValue proposition signals from copy
docs/current/product/monetization.mdMonetization model with evidence
docs/current/product/entitlements.mdEntitlement enforcement mapping
docs/current/product/metrics.mdInstrumentation reality (analytics, flags, events)
docs/current/product/constraints.mdTechnical/business constraints and risks

What It Scans

CategoryPatterns
Routes/screens**/pages/**/*.{tsx,jsx,vue}, **/app/**/page.{tsx,jsx}, React Router, API routes
Value propositionLanding pages, hero sections, taglines, CTA text
Pricing copy**/pricing.*, **/tiers.*, $X/month, tier names (free/starter/pro/enterprise)
Billing codeStripe (stripe.subscriptions, stripe.checkout), PayPal, custom billing gates
EntitlementscanAccess, hasFeature, user.plan, user.tier, middleware guards
Analytics SDKsGA4 (gtag), Mixpanel, Segment, PostHog, Amplitude, Plausible
Feature flagsUnleash, LaunchDarkly, Split.io, Flagsmith, custom FEATURE_/FF_ patterns
ConstraintsRate limiting, file size limits, user limits, trial/expiration, geo-restrictions, compliance (GDPR/CCPA/HIPAA)

Key Points

  • Evidence IDs use namespace E-PRD-NNN (prevents collisions in pack-detect aggregation)
  • 3-layer feature evidence: Surface + Copy + Code Path → confidence mapping:
    • All 3 layers → Confirmed; 2/3 → Firm; 1 layer + heuristics → Tentative; Inferred only → Uncertain
  • Monetization: distinguish "pricing copy" (what product claims) vs "enforcement" (what code enforces) — gates must be proven by code locations
  • Absence of evidence becomes an "absence" evidence item (not a claim without proof)
  • Instrumentation: event taxonomy consistency assessed (naming convention, property standardization, coverage gaps)
  • 4-level confidence: Confirmed / Firm / Tentative / Uncertain

Back to Detect Skills | Back to All Skills