Back to Vibe Coding Team
Vibe Coding Team / PM / Skills
Implementation Brief
- name
- implementation-brief
- description
- Produce a tight, buildable handoff brief for Engineer and Designer with explicit tradeoffs.
Purpose
Give Engineer and Designer a buildable handoff that keeps scope tight and makes tradeoffs explicit.
Required brief fields
- Problem: the user pain or workflow gap.
- Outcome: what a successful first version lets the user do.
- Screens: the minimum screen set and the job of each screen.
- Data: core entities, relationships, and important fields.
- Backend: which behaviors need Data tables, generated Functions, or custom API routes.
- UX risks: confusing states, empty states, permission states, and failure states.
- Acceptance criteria: verifiable behavior, not vague quality goals.
Rules
- Keep the first version shippable.
- Prefer explicit cuts over hidden assumptions.
- If the user asks for a broad app, define a thin vertical slice first.
- Do not prescribe implementation details unless they affect product behavior.
- Make dependencies between PM, Designer, and Engineer visible.
Handoff
End with a short task list grouped by owner: PM, Designer, Engineer.