メニュー
Finish work and reset local environment for next task. Use this when the user is done with a feature branch, wants to clean up after a merged PR, or needs to reset their workspace.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Training plan scheduling, weekly retrospectives, and training adjacent constraint validation. Use this skill whenever the user mentions training, lifts, runs, climbs, the Friday long run, sauna timing, cold plunge timing, recovery days, cutback weeks, altitude weeks, race week, training restructure, Fitbod, asking to schedule a training session, or asking to look back / retrospect on a past training week. Also trigger for "/assist:plan-training", "schedule my long run", "what does training look like this week", "how did last week go", "training retro", or any request that touches the training plan in `Constitution/Fitness/`. Independently usable, and also called by `/assist:plan-week` during Monday planning.
Weekly planning, calendar management, and Monday morning task slotting. Use this skill whenever the user mentions weekly planning, the Monday planning session, slotting tasks, finding free time, checking what their week looks like, moving or swapping calendar events, or wants help fitting something into their week. Also trigger when the user asks about V2MOM measure coverage. Training plan scheduling lives in `assist:plan-training` and meal planning in `assist:plan-meals`; this skill calls into both during Monday planning.
Audit and redesign the context architecture (every CLAUDE.md, learned-rules.md, and tool doc that loads into Claude Code sessions) so load-bearing rules are surfaced and enforced at the point of use rather than scattered, duplicated, or buried. Use this skill whenever Forni says "groom context", "groom-context", "we forgot a basic again", "the context is sprawling", "the rules keep getting lost", "clean up the context", or invokes "/assist:groom-context". Also invoked as a closing step by the monthly path of assist:reflect. This is the cleanup counterpart to assist:codify-context, which writes knowledge into the same architecture.
Craft Business Development emails for RYLLC fractional CTO consultancy. Handles warm reconnects, job posting outreach, rejection follow-ups, VC intros, and custom BD scenarios. Uses established templates and project voice.
Codify knowledge from the current session into the appropriate location in the context architecture using progressive disclosure. Use this skill whenever the user says "codify" followed by a topic, wants to capture something they just figured out, asks to document a pattern or convention, or says something like "we should write this down" or "future me needs to know this." Also trigger when the user discovers a gotcha, foot-gun, or non-obvious behavior worth preserving. Works for both project directories (three-layer CLAUDE.md/README.md pattern) and skill directories (Learned Rules in SKILL.md). Named after the "plan, delegate, assess, codify" Level 4 compounding loop. This is the write-in counterpart to `assist:groom-context`, which audits and prunes the same context architecture.
Triage Gmail inbox by labeling, starring, and archiving emails. Also creates filters for recurring senders. Use this skill whenever the user mentions email triage, inbox cleanup, email labels, email filters, or wants to process their inbox. Default mode is triage.
| name | sdlc:complete |
| description | Finish work and reset local environment for next task. Use this when the user is done with a feature branch, wants to clean up after a merged PR, or needs to reset their workspace. |
| allowed-tools | ["Bash(git *)","Bash(gh *)","Bash(linear *)","Bash(*get-base-branch.sh*)","Bash(*get-linear-issue-id.sh*)","ExitWorktree","AskUserQuestion"] |
Finish the current task and reset the local environment for the next piece of work.
In all bash steps below, substitute placeholder names (like BASE_BRANCH, CURRENT_BRANCH, etc.) with the actual values you stored earlier.
Follow Branch Verification.
If CURRENT_BRANCH equals BASE_BRANCH, note "Already on default branch" and skip to Step 4.
Otherwise, check PR status:
gh pr view --json state --jq '.state'
Store the output as PR_STATE (or "NONE" if the command fails).
Try to extract a Linear issue ID from the branch name:
../../scripts/get-linear-issue-id.sh "CURRENT_BRANCH"
If it succeeds, store the output as ISSUE_ID and update:
linear issue update ISSUE_ID -s "Done"
If the Linear CLI is not available or the command fails, continue silently.
Determine whether the current directory is a linked worktree by comparing the git dir with the common dir. They differ in a linked worktree and match in the main working tree:
git rev-parse --git-dir
git rev-parse --git-common-dir
If the two outputs match, follow Case C. Otherwise, get the worktree path:
git rev-parse --show-toplevel
Store as WORKTREE_PATH. If WORKTREE_PATH contains /.claude/worktrees/, follow Case A. Otherwise, follow Case B.
The worktree lives under .claude/worktrees/, so it was created by sdlc:design via Claude Code's native worktree tools. Try the native tear down first.
Call ExitWorktree with action: "remove". Three outcomes are possible.
The session is the one that created the worktree AND the worktree branch has no commits beyond the original branch. ExitWorktree removes the directory, deletes the branch, and restores the original cwd in one step. Skip to Step 4.
ExitWorktree's safety check uses DAG ancestry, which always fails after a squash merge (the squash commit on main has a different SHA than the worktree branch's commits, even though the content is identical). It also fails for genuinely unmerged work. Use PR_STATE from Step 1 to disambiguate, but always confirm content parity before any destructive action:
If PR_STATE is MERGED: the squash on origin/BASE_BRANCH should contain the worktree's content, but a user could also have added new commits in the worktree after the merge. Verify content parity before discarding:
git diff origin/"BASE_BRANCH"..HEAD --quiet
origin/BASE_BRANCH, so the local commits are genuinely redundant after the squash. Re-invoke ExitWorktree with action: "remove" and discard_changes: true. Skip to Step 4.origin/BASE_BRANCH. Fall through to the AskUserQuestion path below — treat this case the same as OPEN / NONE.If PR_STATE is OPEN, NONE, or MERGED with content divergence: the local commits may represent unpushed work. Do NOT auto-discard. Show the user the unmerged commits:
git log origin/"BASE_BRANCH"..HEAD --oneline
Then use AskUserQuestion to ask whether to:
ExitWorktree with discard_changes: true. Then skip to Step 4.ExitWorktree with action: "keep". Skill stops here; user resolves manually.Common when sdlc:design ran in a previous session, so the current session has no record of having created this worktree. Fall back to manual removal. Get the main worktree path:
git worktree list --porcelain
The first line has the format worktree /path/to/main. Extract the path and store as MAIN_WORKTREE.
Remove the worktree:
git -C "MAIN_WORKTREE" worktree remove "WORKTREE_PATH"
If this fails because the worktree has uncommitted changes, inform the user and advise manual cleanup. Do not pass --force automatically, as that risks losing work.
After successful manual removal, the session's cwd is now a deleted directory. Stop the skill flow here. Do not continue to Step 4, since every subsequent git command would run against a stale cwd and fail. Tell the user:
Worktree removed. Your session cwd is now a deleted directory. Run
cd MAIN_WORKTREEand re run/sdlc:completefrom the main worktree to finish pruning stale branches.
The user's second invocation will land in Case C, which handles the remaining cleanup correctly.
.claude/worktrees/This worktree was not created by sdlc:design. Warn the user and advise manual cleanup. Do not attempt any removal.
Switch back to the default branch and clean up the feature branch:
git checkout "BASE_BRANCH"
git pull origin "BASE_BRANCH"
git branch -d "CURRENT_BRANCH"
The -d flag (lowercase) only deletes if the branch is fully merged, which is a safety net against accidental deletion of unmerged work.
From the main worktree, clean up remote tracking branches that no longer exist:
git fetch --prune
List branches to identify those whose remote was deleted after merge:
git branch -vv
For each branch showing [gone] in the output, attempt deletion. The -d flag uses DAG ancestry, which fails on squash merged branches because the squash commit on BASE_BRANCH has a different SHA than the branch tip. Try -d first; on failure, verify the branch content is identical to BASE_BRANCH and force delete:
git branch -d <branch-name-here>
If that fails with "not fully merged", verify the branch content matches BASE_BRANCH:
git diff "BASE_BRANCH".."<branch-name-here>" --quiet
Exit code 0 means there is no diff (the branch tip's content is identical to BASE_BRANCH, which is the case after a squash merge). Force delete:
git branch -D <branch-name-here>
If the diff is non-empty, do NOT force delete. Warn the user that the branch has content not on BASE_BRANCH and skip it.
git worktree list
git branch --show-current
git status --short
Environment reset complete
Branch: main
Status: (clean)
Ready for next task. Use /sdlc:design <issue-id> to start.