Proposed changes (all with proposal, design, specs, tasks): - app-navigation (9 tasks) — nav bars for both apps - planner-landing-page (7 tasks) — standalone landing page - planner-multiplayer-awareness (13 tasks) — participants, cursors, names - changelog (13 tasks) — public changelog with "what's new" - transactional-emails (15 tasks) — magic link + welcome emails - planner-features (18 tasks) — no-go areas, notes, recovery, rate limits - komoot-import (23 tasks) — Komoot tour import - route-features (37 tasks) — sharing, multi-day, spatial, photos Also adds docs/old-trails-analysis.md with feature analysis from the older trails project. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
708 B
708 B
MODIFIED Requirements
Requirement: Planner home page
The Planner home page SHALL explain the tool's purpose and provide a one-click way to start planning.
Scenario: First-time visitor
- WHEN a user visits planner.trails.cool for the first time
- THEN they see a landing page explaining collaborative route planning, key features, and a prominent "Start Planning" button
Scenario: Start a session
- WHEN a user clicks "Start Planning"
- THEN a new anonymous session is created and the user is redirected to the session view
Scenario: Journal link
- WHEN a user wants to save routes permanently
- THEN a secondary CTA links to trails.cool for account creation