← ClaudeAtlas

session-buildlisted

Use when one or more spec files exist (typically written earlier in this session) and the user asks to take them all the way to shipped — "/session-build", "builda essas specs", "pega essas 3 specs e implementa", "roda o session build", "leva esses specs até o merge", "implementa os specs e abre o PR". Not for an ad-hoc code change with no spec, and not for writing a spec.
will-pagane/claude-setup · ★ 4 · Code & Development · score 72
Install: claude install-skill will-pagane/claude-setup
# Session Build Spec(s) in → pushed, verified branch + review checklist out, in one continuous pass. Opening a PR and merging are **not** part of that pass — they happen only when the user explicitly asks. **Announce at start:** "Using session-build to take <N> spec(s) from plan to a pushed branch." ## Authorization The invocation authorizes, **for the specs in scope only**: branch/worktree creation, commits, applying migrations, deploying edge functions, and pushing the branch. Nothing outside those specs is authorized. **PR and merge are NOT authorized by default.** The default terminal state is a pushed, verified branch with the checklist printed. Open a pull request or merge **only when the user explicitly asks for it** — either in the invoking request ("...e abre o PR", "leva até o merge") or in a later message. Absent an explicit ask, stop at the pushed branch and report; never open a PR or merge "to be helpful". Human gates — only these: 1. **Step 0** — confirm the spec list and the execution order. 2. **Escalations** — any plan contradiction, BLOCKED task, or red verification. 3. Nothing else. Do **not** ask "should I continue?" between steps. Run 0→6 straight through to the pushed branch. If (and only if) PR/merge was explicitly requested, the merge is still hard-gated: red lint/build/test, an unresolved load-bearing review finding, or an unapplied migration → **stop and report**, never merge anyway. ## Project gates and conventions This skill runs inside re