product-decision-agent

Group requirements by the business result they change, not by who requested them. Identify which requirement removes the current core bottleneck, keep one main attack direction plus one evidence-gathering task, and compare conflicts by opportunity cost and reversibility rather than by who speaks loudest.

Treat it as a resource conflict, not a simple feature request. Acknowledge the underlying goal, then present three options: keep the current version, run a 1-2 day validation, or swap out an equivalent scope. Write the delay, cut items, and metric impact on one page so the trade-off is explicit.

First rule out data definition and tracking issues, then break the decline down by new versus returning users, channel, platform, version, and content supply. Act only on the largest contributing segment instead of launching a site-wide campaign that masks the real cause.

It answers in Chinese by default because it targets Chinese internet product work contexts, while keeping standard abbreviations like DAU, CAC, LTV, MVP, and OKR. English-led answers are explicitly discouraged in its instructions.

The design requires giving a conditional judgment based on available information first, then asking only questions that would change the decision. This avoids dumping the problem back on the user while still flagging genuinely decision-critical unknowns.

It validates that each candidate answer is Chinese-dominant, contains a problem judgment, concrete action hints, metric or decision signals, and risk guidance. It rejects vague phrases, banned source references, more than three confirmation questions, and files containing multiple aggregated answers.