菜单
Full sprint flow: /plan -> /execute -> /validate -> /review -> /ship-pr. Always runs /plan (which auto-detects small follow-ups via fast-path). Loops review/execute until clean. End result is a pushed PR.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Ship a feature branch: write docs, bump version, create PR with screenshots and evidence. Links Linear tickets if available. Use when ready to merge.
Functional verification against the plan. Manually confirms every planned path works, takes screenshots, saves API examples as evidence for the PR. Use after /execute.
Build a plan to spec using Red/Green TDD. Writes tests first, confirms they fail, then implements. Supports --ticket mode for scoped execution with dependency checks and file-level scope guardrails. Use after /plan to implement a feature or fix.
Plan a feature or bug fix with deep engineering analysis. Explores the codebase, compares implementation alternatives, maps error paths, and produces test coverage diagrams — all before any code is written. Emits structured YAML tickets with dependency DAG and self-contained agent briefs. Optionally materializes to Linear and TODOS.md. Use when starting new work, breaking down a feature, or before any code changes. Strongly recommended as the first step before /execute.
Analyzes git state, TODOs, and project context to recommend which upstack skill to run next. Use when starting a session or unsure what to do.
Independent exploratory QA. Reads documentation, stands up the app, traverses UI workflows with agent-browser, finds edge cases. Use anytime to test app quality.
| name | upstack-run |
| description | Full sprint flow: /plan -> /execute -> /validate -> /review -> /ship-pr. Always runs /plan (which auto-detects small follow-ups via fast-path). Loops review/execute until clean. End result is a pushed PR. |
_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.
Chains the full sprint flow into a single run. The end result is a pushed PR.
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.
Run /execute against the approved plan. Strict Red/Green TDD: write failing tests, implement until green, atomic commits.
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:
Run /review. Senior engineer code review against the base branch.
If review finds CRITICAL or SECURITY findings:
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.