This round checks the assumptions for mapping Draft Stonk's first activation flow before any `design/` deliverables are written. Confirm, correct, or flag the assumptions, then answer the open questions and compile the YAML at the bottom.
Skill: `user-flow-map`
Resolved mode: flat single-product mode
Resolved topic: `draft-stonk`
Parent command: `$user-flow-map draft-stonk`
Primary source artifacts: `README.md`, `concept.md`, `research/icp.md`, `research/journey-map.md`, `research/positioning.md`, and `research/competitive-analysis.md`.
The primary flow should map a U.S. finance-curious social retail player who wants to turn a market take into a quick, fair fantasy-stock game without real money, prizes, brokerage links, or investment advice.
The flow starts from a market story, stock argument, fantasy-sports analogy, friend challenge, club context, or creator/social feed spark that makes the user want to settle a stock take.
First success is not signup or payment. It is making a first stock pick, finishing a compact snake draft against simple bots, and seeing equal-dollar standings clearly enough to understand who picked better.
The happy path is: understand "fantasy football, but for stocks"; choose a first stock; complete a short snake draft; inspect equal-dollar standings using local, mock, delayed, or clearly labeled data; then replay, share, or invite.
The map should preserve at least four named branches: fastest-to-first-pick, cleanest concept explanation, equal-dollar standings comprehension, and replay/share/invite payoff.
The likely visual UI candidate surfaces are: concept landing/start, first-pick stock chooser, draft board, standings/results, replay/share/invite prompt, and trust/data-label copy. Non-visual surfaces are limited to audit/logging notes for no-advice/data-label state unless you want API/CLI surfaces in scope.
The flow map should exclude real-money trading, cash prizes, brokerage links, account funding, investment recommendations, buy/sell language, production auth, full league administration, and the archived app implementation.
Recommended: map the canonical activation loop from first visit through first completed bot draft and standings, with replay/share/invite as the post-success branch.
Map the canonical activation loop: first visit, concept comprehension, first stock pick, compact snake draft against simple bots, equal-dollar standings, and replay/share/invite as the post-success branch. Exclude full league management and production account systems.Recommended: first-pick speed comes first, because the journey map names first pick as the activation cliff before standings can prove fairness.
Prioritize first-pick speed first, then equal-dollar standings comprehension, then concept explanation, then replay/share/invite payoff. The first pick is the earliest activation cliff; standings cannot prove fairness until the user completes the pick and draft path.Recommended: assume a curated mock/local stock universe of recognizable U.S. tickers with company-name search, because mixed sophistication is a known ICP constraint.
Assume a curated local/mock universe of recognizable U.S. stocks, with company-name and ticker search, duplicate-pick prevention, and plain labels that the data is mock, local, delayed, or prototype-only.Recommended: include lightweight trust copy at concept start, stock chooser, and standings/data label, without making every step feel legalistic.
Place trust-boundary copy in three moments: the start surface for no-money/no-prize/no-advice framing, the stock chooser for pick-not-trade language, and standings for equal-dollar and mock/delayed/local data labeling. Avoid legalistic repetition in the draft board unless a user action could imply trading.Recommended: include friend invite/share and optional club organizer context as handoff notes; exclude payments, brokerage, teacher dashboards, and creator public contests.
Include share/invite to a friend group and optional college-club organizer framing as handoff notes. Exclude payments, brokerage handoffs, teacher dashboards, creator-led public contests, formal approvals, and support operations from this first flow map.| Area | Current round coverage | Likely downstream impact |
|---|---|---|
| Persona, role, and goal | Assumption 1 | Defines who the map serves. |
| Entry points and triggers | Assumption 2 | Defines flow start states. |
| First success condition | Assumption 3 | Defines completion and first value. |
| Happy path | Assumption 4 | Defines ordered flow backbone. |
| Branches and decisions | Assumption 5; branch-priority question | Defines design-tree branches. |
| Surfaces and states | Assumption 6; stock-universe and trust questions | Defines screen/channel candidates and state coverage. |
| Failures and recovery | Open after this round unless you add specifics | Defines errors, no data, validation, and recovery. |
| Handoffs and non-goals | Assumption 7; handoffs question | Defines boundaries and external dependencies. |
Use this after answering. The YAML is routed back to the parent skill so the next session can consume the answers, write the sidecar, and decide whether the confidence gate passes.