Vibe SDD Starter Pack · 03 / 06

Vibe SDD Blueprint Coach

Plan phase by phase and save every approved decision into durable project files.

Vibe SDD Blueprint Coach

What this is

The Blueprint Coach plans your project one phase at a time. It asks one question at a time, shows you the proposed result, waits for confirmation, and then saves the approved file.

Why it matters

A giant prompt can disappear inside one chat. Phase-by-phase files give the project a durable source of truth that another model, tutor, or future session can read.

What to do

Let the coach create or update these outputs in order:

project-brief.md — the user, problem, goal, scope, and proof.
architecture.md — the simple technical structure and constraints.
design.md — the visual direction, layout, and interaction rules.
build-blueprint.md — the approved build sequence and success checks.
build-status.md — the current Work Card, progress, and continuation state.
work-cards/*.md — small implementation jobs with their own verification steps.

Each phase is a gate with a clear pass condition:

Phase	File	Learner action	Pass condition
Brief	`project-brief.md`	Answer project, user, and scope questions	Idea and proof are clear
Architecture	`architecture.md`	Confirm structure, data, and constraints	Build shape is clear
Design	`design.md`	Choose a DesignMD inspiration and translate it safely	Style rules are specific and non-copying
Blueprint	`build-blueprint.md`	Approve the build sequence	No scope creep
Work Cards	`work-cards/*.md`	Approve small cards	First card is buildable

When the coach reaches Design, go through Design Direction before approving build-blueprint.md.

At every phase:

Flow

question -> draft -> learner confirmation -> save file -> next phase

Choose the correct mode when asked:

Vibe 101: Website mode.
Vibe 102: localStorage App mode.
Mini Dashboard: stretch or future work only.

Do not start app code during planning. Check that each approved file exists before continuing. Planning is complete only when build-blueprint.md, build-status.md, and the first current Work Card agree.

Common mistakes

Approving a plan you do not understand.
Letting the AI skip directly from the brief to app code.
Saving decisions only in chat.
Creating Work Cards that are too large to verify.
Continuing when build-status.md points to the wrong card.

Next step

Before approving the Blueprint, lock your visual rules in Design Direction.