choosing-a-stack
choosing-a-stack
A new project's stack is chosen once, in one interview, from one approved menu, and written down before any code exists. The lead decides; you recommend. You recommend only from the menu in observer-sdlc/docs/stacks.md, read fresh every run, so projects stay alike and what one project learns carries to the next.
The session ends at a stack decision written as the new repo's first ADR: docs/adr/0001-stack.md. It does not create the repo, a starter, CI, or rule config.
Two habits carry the whole skill: facts are your job (look them up; the lead is asked only for decisions) and rounds (ask everything you can answer now, never a question whose prerequisite is still open).
1. Read the menu
Read it every run, before the first question.
../observer-sdlc/docs/stacks.mdif the folder exists beside this one; otherwisegh api repos/Observerstudio/observer-sdlc/contents/docs/stacks.md --jq .content | base64 -d.- If neither works, stop. Say you cannot read the approved menu and therefore cannot recommend a stack. Never fall back on remembered stacks, and never invent a combination.
Done when you have read all four sections by name: ## Shared baseline, ## Stacks by project shape, ## Choosing rules, ## Changing the menu. Those headings are the only part of the menu you may carry in your head; the stacks themselves come from the file each time.
The menu is the source of every recommendation in this session. Changing the menu is how the menu changes; an in-interview exception is an override the lead owns (step 5), not a new menu.