Select one branch as the requested result. If not specified, 계획만. Execution or approval of one branch is not authority to execute the next branch, and you do not proceed to the next branch based solely on the plan result or changed files.
| Branch | Input | Result | Approval/stop boundary | Procedure |
|---|---|---|---|---|
| Plan only | Current checkout, actual branch base --base-ref, confirmed --lane·--bump·--no-release |
Affected packages/surfaces, verification order, targetBranch·targetRef·prBase |
Read-only. Does not change Git state, files, or remotes. If the branch value is unknown, submission is not possible. |
impact-plan.md |
| changeset | Base branch, public package candidates | Per-package bump and rationale, Korean draft, after approval .changeset/*.md |
Candidate analysis is read-only. If the bump and wording are not confirmed in the current request, write files only after approval. Do not modify dependency ranges. | changeset.md |
| Submit | Explicit submission request, confirmed plan's targetRef·prBase |
Rebased feature branch, commit, push, PR base | Verify included files/commits, push, and PR creation/base change each within the approval scope of the current request. unknown, stop on changes to the base/remote SHA. |
submit.md |
Both CLIs run directly with Bun from the repository root and output JSON.
bun skills/seed-change/scripts/change-plan.ts --base-ref origin/dev
bun skills/seed-change/scripts/changeset-plan.ts --base-ref origin/dev
There is no execution script for submission. Run the rebase, push, and PR commands directly in the confirmation order of submit.md.