sdlc-vision

# sdlc-vision The opt-in **vision-first** on-ramp. Drop-in (a thin `project.md`, then run goals) stays the default; this is for starting **top-down from a product vision** so every goal is grounded in *why* you're building it. Same `.sdlc/` layout, same spine — just a thicker context layer. 1. **Scaffold the skeleton** if absent (skip-if-exists — never clobbers your edits): `python3 "${CLAUDE_SKILL_DIR}/../sdlc-init/scripts/sdlc_init.py" . --vision` It writes `.sdlc/context/north-star.md` with four tiers to fill. 2. **Draft from the repo first, then refine** — don't hand over a blank page. Read the README, the code structure, and recent git history, write a *first-pass draft* of each tier, then walk the user through refining it. Editing a draft beats filling a blank. Keep each short (direction, not a spec): - **Vision** — draft the change / audience you infer from the README and project; the user corrects. - **Strategy** — draft priorities + **non-goals** from recent commits / open issues; the user sets the real ones (the plan-review alignment gate uses the non-goals). - **Design** — draft the UX shape + the principles a change must respect; the user adjusts. - **Architecture** — draft the rules you develop by as a **numbered, checkable list** from the codebase (layering, dependency direction, boundaries) for the user to approve — plan-review **enforces** these (the stack stays in `project.md`). Write each tier into the file as you ...