Menu
Use after implementation and required verification when PM/coordinator must choose merge, pull request, preserve, discard, or workspace cleanup handling for the current branch.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when an agent needs the shared best-copilot contract for source priority, runtime adapters, init gates, work modes, dispatch packets, review, verification, memory, spec, state persistence, or closeout.
Use inside repo-init-scan after the official stage whenever scaffold verification, bounded repair, or `best-copilot.md` rewrite is still needed.
Use when coordinating large, ambiguous, cross-module, multi-agent, planning, dispatch, fan-in, closeout, or workflow-evolution work as the Senior Project Expert.
Use when maintaining requirements, design, tasks, ADRs, execution-plan state, closeout records, or memory/spec recovery as the Specification Writer.
Use when an approved tasks.md from a Spec Bundle, or a compact approved small-work plan, should be executed by fresh-context specialist subagents, with each task receiving implementation, spec-compliance review, code-quality review, and verification before closure. DO NOT USE FOR: missing plans, brainstorming, or simple single-file edits.
Create the target repository's local spec skeleton and reusable requirements/design/tasks templates. Use from repo-init-scan during first substantial plugin use, or from spec-writing flows when `spec/INDEX.md` or `spec/templates` is missing. Do not overwrite active project specs.
| name | development-branch-closeout |
| description | Use after implementation and required verification when PM/coordinator must choose merge, pull request, preserve, discard, or workspace cleanup handling for the current branch. |
Use this after required reviews and verification have evidence. It turns branch handling into an explicit, safe PM decision.
git status --shortgit branch --show-currentgit rev-parse --git-dirgit rev-parse --git-common-dirgit rev-parse --show-toplevelmain, master, or PM-provided base branch.Use native ask UI when available. Follow the Native Ask Contract from core-workflow-contract for structured ask UI requirements. Present only applicable options:
merge_local: merge to the selected base branch after verification on the merge result.open_pr: push the branch and create a pull request; preserve the worktree for review follow-up.keep_branch: leave branch/worktree as-is and report path, branch, and next manual command.discard: destructive path; requires explicit typed confirmation and a list of commits/files/worktree path that would be removed.If native ask UI is unavailable and a choice is required, follow the Native Ask Contract from core-workflow-contract for fallback behavior.
.worktrees/, worktrees/, or a workspace-isolation artifact. Never remove harness-owned or unknown workspaces.open_pr and keep_branch, preserve the worktree.discard, require exact typed confirmation before deleting anything.Return:
branch_statebase_branchdirty_statusverification_summarydecision_optionsselected_actioncleanup_scoperesidual_risk