菜单
Stage 2 floor migration prompt for /xp-kickoff Step 0. Reads dismissal, prompts customer to set the Stage 2 floor or records a dismissal. INTERNAL — invoked only by xp-kickoff when stage < 2.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Review the completed sprint. Compares what shipped vs planned, updates execution_plan.json milestones with delivered status, and records sprint velocity. Use when all stories are done or deferred.
Create sprint.json from an execution plan milestone or product spec. Decomposes milestones into context-rich stories with file domains, interface contracts, and inlined design context. Deep codebase dive identifies story boundaries. Customer confirms scope before writing.
The universal per-story execution-shape decision. Reads the session default tier and the plan-reviewer's per-story recommendation, then applies a behavior table: it may exit in-agent (no spawn — continue in the existing checkout) or spawn exactly ONE teammate at the chosen tier (the story's executor_model forwarded to spawn_teammate's --model flag). Valid for solo and parallel frontiers alike. Runs once per story after that story's plan is reviewed.
Push the sprint branch, fork xp-close-reviewer for cross-cutting review, and merge into the target with cleanup. Auto-invoked at the end of /xp-sprint-review; degrades gracefully when gh is unavailable.
Verify acceptance criteria for in-progress stories. Present criteria, guide e2e test execution, mark stories done or deferred, update sprint.json.
This skill should be used when the user needs to select work for the session, review retro Try items, triage open questions, or pick sprint stories. Invoked as part of /xp-kickoff or standalone via /xp-work-selection.
| name | xp-stage-migration |
| description | Stage 2 floor migration prompt for /xp-kickoff Step 0. Reads dismissal, prompts customer to set the Stage 2 floor or records a dismissal. INTERNAL — invoked only by xp-kickoff when stage < 2. |
| allowed-tools | ["Bash(python3 */smm/system_context_cli.py get-branching-field *)","Bash(python3 */smm/system_context_cli.py edit-branching-field *)","Bash(python3 */scripts/branching.py *stage)","Bash(python3 -c *datetime*)","Bash(printf *)","AskUserQuestion"] |
Sequential discipline. The harness batches independent tool calls in parallel; this skill is step-gated. Run Step 1 → 2 → 3 strictly, one step per turn — make the call, observe, then decide the next. Never put an
AskUserQuestionand the action consuming its answer in one block (the set-floor/dismiss question vs the edit-branching-field that records it); never spawn the same subagent twice. Independent read-only calls may still batch.
DISMISSED_AT=$(python3 ${CLAUDE_PLUGIN_ROOT}/smm/system_context_cli.py --smm-dir <SMM_DIR> \
get-branching-field stage_prompt_dismissed_at)
If DISMISSED_AT is non-empty, the user has already declined the migration
once. Log to the user (no prompt): "Stage 2 migration prompt was dismissed
at {DISMISSED_AT}. To re-enable, run printf null | python3 ${CLAUDE_PLUGIN_ROOT}/smm/system_context_cli.py --smm-dir <SMM_DIR> edit-branching-field stage_prompt_dismissed_at". Stop without further
steps.
Prompt via AskUserQuestion, substituting the stage value: "This project
is on branching Stage . Stage 2 is the v3.1 plugin floor (sprint branches
required for production-grade discipline). Migrate to the Stage 2 floor now,
or continue at Stage for this session?"
If the user picks migrate, write the Stage 2 floor directly
(system_context.json exists — kickoff Step 0 ran /xp-system-context first):
printf '2' | python3 ${CLAUDE_PLUGIN_ROOT}/smm/system_context_cli.py --smm-dir <SMM_DIR> \
edit-branching-field stage
Do NOT record a dismissal — migration is the non-dismissed branch. Return control to the caller (which re-reads stage fresh, so do not cache).
If the user picks continue, record the dismissal:
TS=$(python3 -c "from datetime import datetime, timezone; print(datetime.now(timezone.utc).isoformat())")
printf '%s' "\"$TS\"" | python3 ${CLAUDE_PLUGIN_ROOT}/smm/system_context_cli.py --smm-dir <SMM_DIR> \
edit-branching-field stage_prompt_dismissed_at