Product Shape & Primary User Journey

There is a prompt instruction at https://www.zangwei.dev/prompts/product-planning/product-shape-primary-user-journey-prompt . Extract and follow the prompt to create file /docs/handbook/planning/product-shape.md

You are a senior Product Manager. Define the product's **Product Shape** and **Primary User Journey**.

## Positioning
This document is not UI design. It defines:
- what the product is in users' minds
- how users repeatedly get core value via one primary path

Product shape sets expectations; the primary journey determines whether it gets used.
This is the key abstraction layer from "idea" to "usable product".

## General requirements
- Start from user perspective, not system/tech perspective
- Focus on the primary journey (not all possible flows)
- Clearly separate core vs auxiliary paths
- Keep shape simple, explainable, reusable

---

## Output structure

1) Product shape
- What type is it in user cognition? (tool / platform / assistant / workflow / system)
- What is the core interaction unit? (page / task / project / conversation / file / template, etc.)
- Basic structure hierarchy:
  - top-level entry
  - core operation area
  - result presentation
- What key expectation should it convey? (speed, certainty, control, automation, etc.)

2) Target user & primary motivation recap
- Who is the target user for the primary journey?
- What context triggers entry?
- What does one complete use aim to solve?
- What is the user's intuitive definition of "success"?

3) Primary user journey
Describe the primary path as steps for completing one "core value loop":
- entry trigger
- first key action
- 2–4 core middle steps
- aha moment (when value is realized)
- end state (save, share, reuse, re-enter)

4) Decision points & frictions
- Where do users get confused or drop off?
- Which steps are required vs deferrable?
- Which frictions are justified vs should be removed?
- What information must be communicated explicitly?

5) Auxiliary paths & non-core flows
- Which paths serve the primary journey? (settings, management, import, history, etc.)
- Which paths can be omitted in MVP?
- How to ensure auxiliary paths do not dilute primary clarity?

6) Alignment with success criteria & boundaries
- Does the primary journey directly support the North Star metric?
- Any paths that drift from core value?
- Are boundaries reflected clearly in the journey?
- Any "tempting" features that seem important but do not belong in the primary journey?

---

## Output requirements
- No UI mockups, no implementation
- No long feature lists
- Use the user's step-by-step actions as the narrative
- If the primary journey cannot be described clearly, call it out as a risk signal

End with 3–5 bullet points:
"Is this product shape and primary journey sufficient to deliver core value?"