Upsolve-Labs Update Check (run first)
_UPD=$(~/.claude/skills/upstack/bin/upstack-update-check 2>/dev/null || .claude/skills/upstack/bin/upstack-update-check 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true
If output shows UPGRADE_AVAILABLE <old> <new>: read ~/.claude/skills/upstack/skills/upgrade/SKILL.md and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If JUST_UPGRADED <from> <to>: tell user "Running upstack v{to} (just updated!)" and continue.
Upstack Run
Chains the full sprint flow into a single run. The end result is a pushed PR.
Step 1: Plan
Always run /plan. The /plan skill has its own Fast-Path Check that detects when a plan already exists in context and the new request is a small follow-up — in that case it skips full ceremony and produces a lightweight amendment. If the change is complex, /plan runs its full flow. Either way, do NOT proceed until /plan completes.
Step 2: Execute
Run /execute against the approved plan. Strict Red/Green TDD: write failing tests, implement until green, atomic commits.
Step 3: Validate
Run /validate. Walk through every planned path manually, capture evidence (screenshots, API examples) to evidence/.
IMPORTANT: Do NOT skip /validate when UI files are in the diff. "Playwright tests pass" is NOT a substitute for /validate. Tests verify assertions; validate produces evidence (screenshots, API examples) for the PR and catches visual/UX issues that assertions miss.
If validation finds gaps:
- Amend the plan with the gaps.
- Loop back to Step 2 (/execute) to close them.
- Re-validate. Maximum 3 loops before stopping and reporting to the user.
Step 4: Review
Run /review. Senior engineer code review against the base branch.
If review finds CRITICAL or SECURITY findings:
- Automatically fix the flagged issues (treat them as if the user said "fix all").
- Loop back to Step 2 (/execute) for the fixes.
- Re-run /review. Maximum 3 review/execute loops before stopping and reporting to the user.
Step 5: Ship (MANDATORY — do not skip)
Run /ship-pr. This step MUST execute — it handles documentation, version bump, and PR creation. All three are required outputs of /upstack-run. The version bump question is the only interactive pause. If you have reached this step, do not end the conversation without completing /ship-pr.
Guardrails
- Max loops: 3 for validate gaps, 3 for review findings. If still failing after 3, stop and report what remains.
- Abort on hard failure: If tests cannot pass, gh is unavailable, or the branch is in a bad state, stop and report. Do not retry endlessly.
- No silent skips: Always announce which step you are entering and whether any steps were skipped or looped.