# First task, first win

## Intent and first success
A first-time user of this fictional task app needs a useful result before setup becomes a barrier. First success is one saved task, visible under “Your tasks” and still present after reload.

## Approaches and decision
1. **Immediate first-task creation:** Welcome → first-task form → dashboard. It gives value quickly and keeps recovery close to the input, but provides no account identity or cross-device recovery.
2. **Signup-first onboarding:** Welcome → account registration → first-task form → dashboard. It could support identity and later synchronization, but delays value and requires excluded account/backend work.

Recommend immediate creation. This fixed-scope decision is the **demo author’s choice**, supplied by the fixture; it is not a user-interview finding or human approval. Further discovery is waived for this sample.

## Required behavior
- **FR-001:** Welcome offers Get started, leading to the first-task form.
- **FR-002:** Label the title Your first task; Back preserves typed text.
- **FR-003:** Blank or whitespace-only input shows Enter a task name. and creates no task.
- **FR-004:** Trim titles, require 1–80 characters, and render them as text.
- **FR-005:** Disable Create task during save, show Saving…, and create only one task on double submission.
- **FR-006:** Fail next save triggers an error; retain the title and allow a successful retry.
- **FR-007:** Success shows Your tasks and the saved title; reload preserves the task.
- **FR-008:** Show keyboard focus and fit widths of 320px, 390px, and 1280px.

## Constraints and exclusions
Use Node 24 and plain HTML/CSS/JavaScript with the supplied local storage adapter. No signup, backend, remote API, analytics, real user data, external assets, accounts, dependencies added, or deployment. Never treat input as HTML. Lost input, duplicate creation, and unrecoverable save errors are failures.

This stage produces documentation only. Preserve existing files, checks, dependencies, and installed skills. A future disposable prototype remains distinct from final application implementation, which comes after plan review; neither is built here.

## Questions for a real product owner
Who is the primary audience and their first likely task? What evidence would define onboarding success? What local-data retention and deletion expectations apply? Would future cross-device access justify an account step?