One-shot: implement and open a PR - Brightstack Intro Tutorial

Once the project looks good, tell Bright to implement what it can:

Happy with the project. Let’s start implementing what you can.

What Bright takes vs what you take

Bright typically owns engineering issues and waits on account/config work only you can do. Bright handing off engineering work and listing user setup steps

Bright handing off engineering work and listing user setup steps

Goal and task panel showing clone, API route, and form wiring

Example split (Poke Feed + Sender)

Bright (Engineer)	You
Build `/api/subscribe` with validation + provider API call	Create a free Sender (or chosen provider) account
Wire hero + footer signup forms	Create subscriber list + enable double opt-in
Push a branch and open a PR	Generate API key; add env vars on Vercel

Example env vars (names depend on the recommended provider):

SENDER_API_KEY=...
SENDER_LIST_ID=...

What “done” looks like

Same as the step-by-step path: Bright connects to GitHub, creates a branch, updates the codebase, and opens a pull request. Your job is review → approve → merge.

If Bright can’t reach the repo (access / 404), connect GitHub or grant repository access, then retry.

One-shot vs step-by-step

	Step-by-step	One-shot
Modes	Ask → Plan → Agent	Stay in Agent
Checkpoints	Review research, then plan, then execute	Fewer pauses; review after project creation
Best for	Teams / safer scoping	Solo builders / prototypes / full-cycle owners