[P0] Curator Streak Chat Flow — Service Preview Handoff & UX #6

New Issue

puter · 2026-06-15T15:46:28Z

puter commented

2026-06-15 15:46:28 +00:00

Requirements

When a user clicks a daily/weekly streak suggestion in the dashboard, the curator chat must guide them through a focused conversation that produces a service preview CTA — not a blank setup screen — so they can immediately start the intended service (interview, roleplay, resume, etc.) with sensible defaults.

What Good Looks Like

User clicks "Practice behavioral interview" → gets asked at most 1 clarifying question → sees a card with "Open interview preview" → lands directly on preview with role/type/difficulty pre-filled.

Acceptance Criteria

Curator prompt externalized to markdown file (editable without code redeploy)
Interview handoff returns /agents/interview/preview route, not /setup
Roleplay handoff returns preview route, not setup
Status is handoff_ready when sufficient context exists (max 1 clarifying question)
Default params: type=behavioral, difficulty=medium, duration=5
Onboarding-derived role pre-filled when available
No internal route leaks in chat text
Build passes on VPS (npm run typecheck && npm run build)

Edge Cases

Vague answer → one follow-up, then preview with best guess
No onboarding role → ask "What role are you targeting?" then preview
Service down → friendly message, no broken link
Mobile → full-screen modal, thumb-friendly CTA

docs/requirements-curator-streak-chat-flow.md (full requirements)
docs/curator-30day-examples-by-icp.md (30-day plans & prompt templates)
docs/curator-icp-comprehensive-playbook.md (service definitions)

Definition of Done

All acceptance criteria pass on staging
Staging VPS stable (no crashes, no 500s)
User can click suggestion → chat → preview CTA → preview page → start service in ≤5 interactions
Changes committed to staging-rosh

## Requirements When a user clicks a daily/weekly streak suggestion in the dashboard, the curator chat must guide them through a focused conversation that produces a **service preview CTA** — not a blank setup screen — so they can immediately start the intended service (interview, roleplay, resume, etc.) with sensible defaults. ## What Good Looks Like User clicks "Practice behavioral interview" → gets asked at most 1 clarifying question → sees a card with "Open interview preview" → lands directly on preview with role/type/difficulty pre-filled. ## Acceptance Criteria 1. Curator prompt externalized to markdown file (editable without code redeploy) 2. Interview handoff returns `/agents/interview/preview` route, not `/setup` 3. Roleplay handoff returns preview route, not setup 4. Status is `handoff_ready` when sufficient context exists (max 1 clarifying question) 5. Default params: `type=behavioral`, `difficulty=medium`, `duration=5` 6. Onboarding-derived role pre-filled when available 7. No internal route leaks in chat text 8. Build passes on VPS (`npm run typecheck && npm run build`) ## Edge Cases - Vague answer → one follow-up, then preview with best guess - No onboarding role → ask "What role are you targeting?" then preview - Service down → friendly message, no broken link - Mobile → full-screen modal, thumb-friendly CTA ## Related - `docs/requirements-curator-streak-chat-flow.md` (full requirements) - `docs/curator-30day-examples-by-icp.md` (30-day plans & prompt templates) - `docs/curator-icp-comprehensive-playbook.md` (service definitions) ## Definition of Done - All acceptance criteria pass on staging - Staging VPS stable (no crashes, no 500s) - User can click suggestion → chat → preview CTA → preview page → start service in ≤5 interactions - Changes committed to `staging-rosh`

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: growqr-app/growqr-backend#6