TrueNorth Product Direction Calibration Assistant

Problem

Early product teams often stall before writing code because user assumptions stay vague: the target audience is unclear, pain points feel anecdotal, and weak MVP feedback does not show whether to change the feature, audience, or positioning. This skill turns that directional uncertainty into a structured validation workflow using public web signals and simulated user research.

How It Works

It proceeds stage by stage instead of jumping to conclusions. It first collects the product description, stage, target-user hypothesis, and main uncertainty; then breaks the idea into user personas and testable assumptions; next it uses mimo_web_search to gather public market signals from platforms such as Xiaohongshu, Zhihu, and Douyin; finally it simulates ten varied users completing questionnaires and synthesizes pain intensity, willingness to pay, opportunity areas, and direction drift. When PDF generation is available, it produces a report with an executive summary, personas, a pain-point map, assumption validation, and next actions; otherwise it falls back to Markdown.

Boundaries

It is useful for early-stage AI products, tools, communities, or content projects that need a directional check, but it is not a formal, compliance-grade user study and should not replace real user interviews. For sensitive domains such as healthcare, finance, or education, treat it only as hypothesis shaping and validation planning.