Audit a codebase for product-market fit readiness -- evaluate startup PMF signals, core value loop tightness, feature scatter vs focus ratio, user activation funnel friction, retention hook infrastructure, pricing flexibility, analytics event coverage, CI/CD iteration speed, and growth-stage maturity for pre-seed through Series A products.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
You are an autonomous product-market fit analyst. Do NOT ask the user questions. Read the actual codebase, evaluate every PMF signal you can extract from code and architecture decisions, and produce a comprehensive PMF readiness report.
PMF is not just a business metric -- it leaves fingerprints in the code. A product approaching PMF has a tight core loop, minimal distractions, fast iteration speed, and instrumentation to measure what matters. A product far from PMF has scattered features, no analytics, slow deploys, and an architecture that cannot adapt.
TARGET: $ARGUMENTS
If arguments are provided, use them to focus the analysis (e.g., specific feature area, target market segment, growth stage). If no arguments, run the full analysis.
Step 1.1 — Product Discovery
Read the project's README, package metadata, landing page copy, app store description, and marketing materials. Summarize:
Step 1.2 — Critical Path Trace
Identify the ONE core user flow that delivers the primary value. This is the "aha moment" path — the sequence of actions where a user first experiences the product's value.
Trace this path end-to-end through the codebase:
For each step, record:
Step 1.3 — Core Path Health Score
Evaluate the critical path:
Score: 0-10 (0 = core path is broken, 10 = flawless value delivery)
Determine whether engineering effort is concentrated on core value or dispersed across distractions.
Step 2.1 — Feature Inventory
Scan the entire codebase and categorize every user-facing feature:
Core Features — directly deliver the primary value proposition:
Supporting Features — enable core features but don't deliver value alone:
Peripheral Features — nice-to-have, don't relate to core value:
Abandoned/Incomplete Features — started but not finished:
Step 2.2 — Code Distribution
Calculate approximate lines of code per category:
Step 2.3 — Git History Analysis (if git available)
Analyze recent commit history to understand where effort is going:
git log --oneline -100 to get recent commitsStep 2.4 — Fix Ratio
Count commits that are fixes vs new features:
Score: 0-10 (0 = scattered effort, 10 = laser-focused on core value)
Evaluate how effectively the product converts new users into active users.
Step 3.1 — Signup to Value Steps
Count every required step between "I want to try this" and "I got value":
Record the total step count and identify every friction point.
Step 3.2 — Activation Barriers
Search for code that creates unnecessary friction:
Step 3.3 — Activation Metrics
Search for tracking of activation events:
Step 3.4 — Activation Optimization Infrastructure
Check if the team can experiment with activation:
Score: 0-10 (0 = high friction, no measurement, 10 = optimized, instrumented funnel)
Evaluate whether the product is built to bring users back.
Step 4.1 — Engagement Hooks
Search for retention mechanisms in the codebase:
Step 4.2 — Engagement Loop Quality
For each hook found, evaluate:
Step 4.3 — Churn Prevention
Search for signals that the team is thinking about churn:
Step 4.4 — Network Effects
Search for features that increase value as more users join:
Score: 0-10 (0 = no retention infrastructure, 10 = strong engagement loops + network effects)
Evaluate whether the architecture supports pricing experimentation.
Step 5.1 — Current Pricing Model
Search for pricing, plan, tier, and subscription logic:
Step 5.2 — Pricing Flexibility
Evaluate how easily the team can change pricing:
Step 5.3 — Revenue Readiness
Check for revenue infrastructure maturity:
Score: 0-10 (0 = no monetization, 10 = flexible, instrumented revenue engine)
Evaluate whether the team can actually measure PMF signals.
Step 6.1 — Analytics Implementation
Search for analytics/tracking across the codebase:
Step 6.2 — PMF-Critical Metrics Coverage
Check if these essential PMF metrics are trackable from the codebase:
Activation:
Engagement:
Retention:
Revenue (if applicable):
Step 6.3 — Experimentation Infrastructure
Check for A/B testing and experimentation capability:
Score: 0-10 (0 = flying blind, 10 = comprehensive PMF measurement)
Evaluate how fast the team can ship changes — critical for finding PMF.
Step 7.1 — Development Pipeline
Check for CI/CD and deployment infrastructure:
Step 7.2 — Code Modularity
Evaluate how easy it is to change things:
Step 7.3 — Velocity Indicators (from git if available)
Score: 0-10 (0 = slow, manual, fragile deploys, 10 = fast, automated, safe iteration)
Look for signals that the product is connecting with its market.
Step 8.1 — Integration Ecosystem
Search for third-party integrations:
Integration breadth signals market pull — the market is telling you to connect with their existing tools.
Step 8.2 — Multi-Market Readiness
Check for internationalization and localization:
Step 8.3 — Platform Coverage
Check deployment targets:
Broader platform coverage can signal market demand pulling the product to new surfaces.
Score: 0-10 (0 = isolated product, 10 = ecosystem-integrated, multi-market ready)
Write the complete analysis to docs/pmf-analysis.md in the project
(create the docs/ directory if it doesn't exist).
After producing output, validate data quality and completeness:
IF VALIDATION FAILS:
IF STILL INCOMPLETE after 2 iterations:
| Dimension | Score | Weight | Weighted | Key Finding |
|---|---|---|---|---|
| Core Value Delivery | {0-10} | 25% | {score} | {one-line finding} |
| Feature Focus | {0-10} | 15% | {score} | {one-line finding} |
| User Activation | {0-10} | 15% | {score} | {one-line finding} |
| Retention Infrastructure | {0-10} | 15% | {score} | {one-line finding} |
| Pricing Flexibility | {0-10} | 5% | {score} | {one-line finding} |
| Analytics Maturity | {0-10} | 10% | {score} | {one-line finding} |
| Iteration Speed | {0-10} | 10% | {score} | {one-line finding} |
| Market Signals | {0-10} | 5% | {score} | {one-line finding} |
| PMF Readiness | {weighted avg}/10 | {verdict} |
PMF Stage: {SEARCHING / APPROACHING / ACHIEVED / SCALING}
| # | Gap | Dimension | Impact | Effort | Recommendation |
|---|---|---|---|---|---|
| 1 | {description} | {dimension} | {High/Med/Low} | {S/M/L} | {specific action} |
| 2 | ... | ... | ... | ... | ... |
Actions that would most rapidly improve PMF readiness:
Factors that could prevent or delay PMF:
docs/pmf-analysis.md============================================================
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /pmf-analysis — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}
Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
NEXT STEPS:
/iterate to address the top PMF gaps."/customer-success-audit to strengthen retention and support infrastructure."/growth-audit to build acquisition and engagement loops."/compete to validate differentiation against competitors."/stress-test-personas to pressure-test the product from adversarial angles."/cost-analysis to ensure unit economics support the business model."No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Run a full Section 508 + WCAG 2.2 Level AA accessibility audit on a federal / .gov / public-sector website or ICT product. Triggers: "Section 508", "508 audit", "WCAG", "VPAT", "ACR".
The English summary is being prepared. Showing the original description.
Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards..
The English summary is being prepared. Showing the original description.
Analyzes advertising yield across programmatic and direct-sold inventory including CPM/CPC/CPA performance, header bidding efficiency, fill rate optimization, inventory monetization strategies, and compliance with IAB standards and OpenRTB protocols..
The English summary is being prepared. Showing the original description.
Create and manage Architecture Decision Records using the Michael Nygard format. Triggers: you need to document architecture decisions, record technical choices, explain why a technology was chosen.
The English summary is being prepared. Showing the original description.
Analyzes affordable housing management software for unit allocation algorithms, waitlist management, income verification workflows, Fair Housing compliance, LIHTC and Section 8 program tracking, inspection scheduling, and tenant reporting..
The English summary is being prepared. Showing the original description.
Rewrites existing landing pages, blog posts, and documentation so AI search engines (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini) cite them. Triggers: an existing page underperforms in AI answers despite ranking well in classic SERPs.
The English summary is being prepared. Showing the original description.