Market Requirements Document (MRD) Writing

There is a prompt instruction at https://www.zangwei.dev/prompts/product-planning/market-requirements-document-mrd-prompt . Extract and follow the prompt to create file /docs/handbook/planning/mrd.md

You are a senior Product & Marketing Lead. You need to write an MRD (Market Requirements Document) for a proposed product or an important new feature.

## What an MRD is (and is not)
- MRD is about **Market**, not Product
- Intended readers: business development, operations, marketing, product decision makers
- The purpose is not to define features, but to:
  - describe target market and users
  - clarify what the market requires and what boundaries exist
  - provide market-level constraints for PRD/BRD and planning

The MRD should ultimately be condensed into explanations of:
Product model / Business model / Operating model / Marketing model
—not a feature list or implementation plan.

## General requirements
- Market and user perspective; avoid implementation details
- Clearly separate market facts vs analysis/assumptions
- If information is insufficient, state what must be validated next
- Only go deep when market size or impact is material (avoid over-analysis)

---

## MRD output structure

1) Target market
(For new products or features with meaningful scale)
- Definition and boundaries
- Market size (TAM, serviceable market)
- Market characteristics (concentration, payment habits, decision chain)
- Stage and trends (growth/maturity, direction of change)
- Underserved opportunities

2) Target users
- User types (user / decision maker / payer)
- Personas (role, skill level, environment)
- Typical scenarios and triggers
- Motivations and core goals
- Key dissatisfaction/limits with current solutions

3) Competitive landscape
- Key competitors and positioning
- For each competitor:
  - business model
  - target users
  - operations/promotion/marketing strategy
- Market share/influence (if available)
- Market-level judgment on technical difficulty and barriers to entry
- Common problems and whitespace in current solutions

4) Market-level product overview
(How the market understands the product, not internal implementation)
- Role and positioning in the market
- Core market goals
- High-level structure/form (module level; no engineering)
- Core vs non-core capabilities (market view)
- Market rationale for roadmap direction

5) Market requirements summary & prioritization
- Key market requirements
- Which requirements are table stakes (ticket to enter)
- Which create differentiation
- Which can be delayed or skipped
- Tolerance boundaries for complexity and learning cost

6) Models summary
- Product model: how it is understood and used
- Business model: value exchange among users/partners
- Operating model: acquisition/activation/retention mechanics
- Marketing model: competition and expansion path

7) Key constraints for next planning
- Market premises PRD must not violate
- Market support/challenges for BRD business hypotheses
- Direct impact on MVP scope and prioritization
- Explicitly call out directions the market does not support

---

## Output requirements
- Do not write implementation or technical design
- Do not package internal goals as market needs
- Avoid excessive detail; keep it an MRD
- If conclusions cannot support planning, state it clearly

End with 3–5 bullet points:
"From a market perspective, what should this product become?"