whisper-lolo-roadmap
Guide development of the whisper-lolo project based on specifications-projet.md. Use when planning or executing a sprint/PR, validating scope or constraints, or aligning architecture, statuses, and DoD for the Next.js + Vercel + Blob + Inngest + Whisper stack.
When & Why to Use This Skill
The whisper-lolo-roadmap skill is a specialized development assistant designed to manage the lifecycle of Next.js and Whisper-integrated projects. It ensures technical alignment by enforcing architectural constraints, guiding sprint execution, and validating Pull Requests against a rigorous Definition of Done (DoD) for stacks involving Vercel Blob and Inngest.
Use Cases
- Sprint Planning & Scope Validation: Use the skill to confirm which sprint (0-5) a task targets and ensure the scope remains within the predefined goals to prevent project creep.
- Architectural Guardrail Enforcement: Automatically verify that development adheres to non-negotiable rules, such as avoiding audio uploads via Next.js API routes and ensuring asynchronous processing.
- Data Model & Status Management: Maintain consistency in recording and transcription statuses (e.g., transcribing, uploaded, done) across the application's logic.
- Definition of Done (DoD) Compliance: Check if a PR meets specific technical milestones, such as stable 10-minute recording handling or successful Inngest job triggers.
- Technical Documentation Reference: Quickly align code changes with the project's specifications-projet.md and Vercel/Inngest integration guides.
| name | whisper-lolo-roadmap |
|---|---|
| description | Guide development of the whisper-lolo project based on specifications-projet.md. Use when planning or executing a sprint/PR, validating scope or constraints, or aligning architecture, statuses, and DoD for the Next.js + Vercel + Blob + Inngest + Whisper stack. |
Whisper Lolo Roadmap
Overview
Apply the project roadmap and constraints to keep each PR aligned with the sprint goals, status model, and non-negotiable rules.
Workflow
1) Identify the sprint and scope
- Confirm which sprint (0..5) the task targets.
- Keep the PR limited to one sprint and its Definition of Done.
- When unsure, ask which sprint the change belongs to.
2) Re-assert hard constraints
- Never upload audio via a Next.js API route.
- Never wait for transcription inside an HTTP request.
- Always chunk, store, upload direct, then process async.
- Chunk before transcription.
3) Maintain data model and statuses
- Use
recordings.status: draft | recording | uploaded | transcribing | done | error. - Use
transcriptions.status: pending | done | error. - Update status transitions explicitly in code paths.
4) Apply sprint DoD checks
- Sprint 0: migrations applied, endpoint test ok,
/recordreachable. - Sprint 1: 10 minutes stable, refresh restores chunks, blob playable.
- Sprint 2: long upload ok, Blob URL reachable, DB updated.
- Sprint 3: event received, job starts automatically.
- Sprint 4: transcription stored, errors handled, logs clear.
- Sprint 5: status shown, text rendered, copy/export works.
5) Reference project docs
- Read
specifications-projet.mdfor the authoritative roadmap. - Use
documentation/summaries to confirm API behaviors.
Key decisions to preserve
- Next.js App Router + TypeScript.
- Inngest for long-running jobs.
- Vercel Blob client uploads.
- Provider abstraction for Whisper now, Voxtral later.
References to consult
specifications-projet.mddocumentation/vercel-blob-overview.mddocumentation/vercel-blob-sdk.mddocumentation/inngest-background-jobs.mddocumentation/openai-node-audio-example.md