review · alignment date 2026-06-15 · visual tier

Draft Stonk Journey Map Framework Selection

This review page proposes the journey-map scope and framework queue before any `tasks/todo.md` mutation. It is scope evidence only: no journey findings, rankings, or canonical journey-map deliverables have been synthesized.

Scope Evidence

Research Scope

Flat `research/` mode for Draft Stonk. No `research/.progress.yaml` product-path manifest was found, and no non-archived `research/{slug}/` product directory is present.

Hard Prerequisite

`research/icp.md` exists, so the journey-map prerequisite is satisfied.

Product State

`README.md` and `CLAUDE.md` state the repository is a fresh-start prototype seed with no active app scaffold, dev server, test command, build command, or live product.

Detected Mode

Detected mode: Pre-Product (hypothesized).

Detection Signal	Observed Scope Evidence	Mode Impact
No active production app or live users detected	`CLAUDE.md` says there is no active app scaffold, development server, test command, or build command after reset.	Supports pre-product mode.
No post-launch customer feedback file	No `research/customer-feedback.md` file was found.	Supports pre-product mode.
User invocation did not request product shortcut	Invocation was `$journey-map`, not `$journey-map product`.	Uses Mode A framework selection.

Required Gate: Mode Confirmation

Approve pre-product mode for this journey-map queue.

Other / None of the above

Need clarification

Available Evidence

Source Category	Status	Use Before Approval
`research/icp.md`	Present	Scope evidence for audience, triggers, current alternatives, pain map, and value drivers.
`research/competitive-analysis.md`	Present	Scope evidence for substitute landscape and product constraints.
`README.md`, `CLAUDE.md`	Present	Scope evidence for fresh-start status and no-money/no-prize/no-advice constraints.
`research/customer-feedback.md`	Absent	Supports pre-product mode; no post-launch grounding available.
`research/journey-map-*.md`	Absent	No framework outputs exist yet; synthesis is not ready.

Framework Selection

Select the frameworks to queue. Pre-product defaults are pre-checked.

JTBD Timeline default
Moesta/Switch timeline with push, pull, anxiety, and habit forces. Recommended because Draft Stonk is still validating the switch from current alternatives to a social stock draft.

Experience Map default
Adaptive Path emotional arc with doing, thinking, and feeling layers. Recommended because the first loop depends on comprehension, confidence, social payoff, and replay desire.

Customer Journey Canvas optional
Stage x touchpoints x actions canvas. Useful if you want broader lifecycle coverage before UX variation work.

Service Blueprint optional
Front-stage, backstage, and support lines. Optional now because no active service or operations layer exists yet.

User Story Map optional
Activity, task, and story hierarchy. Optional now; stronger after the switching and experience assumptions are sharper.

Required Gate: Framework Queue

Approve the selected framework checkboxes above.

Other / None of the above

Need clarification

Execution Plan Preview

After final compiled YAML approval, the selected frameworks will be written to `tasks/todo.md` for sequential `$exec` execution, followed by synthesis. The parent `journey-map` skill does not execute child frameworks itself.

## Journey Map Framework Execution

- [ ] Run `$journey-map/frameworks/jtbd-timeline` -- JTBD switching timeline
- [ ] Run `$journey-map/frameworks/experience-map` -- Adaptive Path experience map
- [ ] Synthesize: `$journey-map --synthesize` -- Combine framework outputs into research/journey-map.md

Assumptions & Confidence

Assumption	Confidence	What Would Change It
Flat `research/` scope is correct.	High	A hidden active product-path manifest or explicit user correction.
Pre-product mode is correct.	High	Evidence of live users, active product code, or post-launch feedback.
JTBD Timeline and Experience Map are the right defaults.	Medium	User preference for operational/service mapping first, or evidence that a running product already exists.
No synthesized journey-map output should be written yet.	High	Final compiled YAML approving the framework queue and subsequent framework outputs.

Required Gate: Research Completeness For Queueing

Evidence is sufficient to queue journey frameworks.

Other / None of the above

Need clarification

Artifact Destination & Proposed File Changes

Path	Timing	Mutation
`alignment/journey-map-draft-stonk.html`	Now	Review page for framework-selection approval.
`alignment/index.html`	Now	Central index updated to include this review page.
`prompts/journey-map/skill-prompt-20260615-115533-draft-stonk.md`	Now	Prompt-history capture for this skill invocation.
`tasks/todo.md`	After final compiled YAML only	Append or update the selected framework queue and synthesis step.
`research/journey-map.md`	Not in this stage	No synthesis output is proposed until child framework outputs exist and synthesis approval occurs.

Required Gate: File Changes

Approve updating `tasks/todo.md` after final YAML, limited to the selected framework queue and synthesis step.

Other / None of the above

Need clarification

Compile YAML

Use feedback YAML for revision requests before final approval, or compile final answers after all required gates are answered.

Required questions remaining: 4