メニュー
Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links. Use when a plan has 2+ sequentially dependent changes.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/athola/claude-night-market --skill stack-createコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| name | stack-create |
| description | Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links. Use when a plan has 2+ sequentially dependent changes. |
| alwaysApply | false |
| category | workflow-automation |
| tags | ["git","stacked-diffs","pr","branches","planning"] |
| tools | [] |
| complexity | medium |
| model_hint | standard |
| estimated_tokens | 800 |
| dependencies | ["sanctum:git-workspace-review","sanctum:do-issue"] |
Initialize a stacked branch set from a multi-step plan. Each logical slice of the plan becomes one branch targeting the previous slice's branch as its base.
Use stack-create when a plan produces 2 or more ordered
changes where each change depends on the previous one
completing (and merging) before it can land.
For independent changes, use parallel worktrees instead
(see egregore).
sanctum:stack-push)git version | awk '{print $3}' to check)gh CLI authenticateddo-issue or
attune:blueprint)git status)Create TodoWrite items before starting:
stack-create:git-version-checkedstack-create:slices-identifiedstack-create:branches-createdstack-create:stack-verifiedgit-version-checked)git version
Confirm the output is 2.38.0 or higher.
If not, the --update-refs flag is unavailable.
Warn the user and fall back to manual branch tracking.
Check for optional jj accelerator:
if command -v jj &>/dev/null && jj root &>/dev/null 2>&1; then
echo "jj available"
else
echo "using git --update-refs"
fi
slices-identified)Read the plan and extract ordered slices. Each slice must satisfy:
Example slices for a plan with three parts:
Slice 1: add-schema -- database schema changes
Slice 2: add-api -- API layer (depends on schema)
Slice 3: add-ui -- frontend (depends on API)
Record the slice list before creating branches.
branches-created)Starting from the base branch (usually master or main):
BASE=master
STACK=stack/my-feature
# Slice 1 branches from master
git checkout -b ${STACK}/add-schema ${BASE}
# Slice 2 branches from slice 1
git checkout -b ${STACK}/add-api ${STACK}/add-schema
# Slice 3 branches from slice 2
git checkout -b ${STACK}/add-ui ${STACK}/add-api
Convention: stack/<feature-name>/<slice-name>
Return to the first slice branch to begin work:
git checkout ${STACK}/add-schema
# jj creates an empty commit on each branch automatically
# Use jj new to move to a new change
jj new -m "stack: add-schema" --no-edit
stack-verified)Confirm the branch topology is correct:
git log --oneline --graph \
${BASE}..${STACK}/add-ui
Each slice branch should appear as a linear chain above the base.
If jj is available:
jj log --revisions \
"ancestors(${STACK}/add-ui, 10) & !ancestors(${BASE})"
stack-push to
open PRs, or work slice-by-slice and push when readystack-create:git-version-checked
through stack-create:stack-verified) are created before branch
creation starts and marked complete in orderstack/<feature-name>/<slice-name>git log --oneline --graph <base>..<tip> shows a linear chain
with each slice branch appearing in dependency orderTurn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.
Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.