Menú
Use before approved implementation plans or substantial feature/fix work when workspace isolation, branch provenance, setup baseline, or worktree safety must be decided.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | workspace-isolation |
| description | Use before approved implementation plans or substantial feature/fix work when workspace isolation, branch provenance, setup baseline, or worktree safety must be decided. |
Use this before substantial implementation starts. The goal is to protect the user's current checkout and create baseline evidence without fighting the runtime.
NEEDS_CONTEXT when the packet lacks workspace, branch, or baseline facts.git rev-parse --show-toplevelgit rev-parse --git-dirgit rev-parse --git-common-dirgit rev-parse --show-superproject-working-treegit branch --show-currentgit status --shortgit-dir and git-common-dir differ and the repo is not a submodule, treat the checkout as already isolated. Record path, branch or detached state, and skip worktree creation.git worktree when the host runtime owns isolation..worktrees/ directory.worktrees/ directory.NEEDS_USER_INPUT with options: add an ignored .worktrees/, use a user-named location, or work in place..github/instructions/project.instructions.md. If those commands are unknown or fail, report the blocker before implementation..gitignore, create external directories, or run network-heavy setup unless authorized by PM/top-level flow and tool permissions.development-branch-closeout.isolation_status=blocked and continue only if PM chooses work-in-place or stops the task.Return or record these fields in the PM packet:
workspace_pathbranch_stateisolation_status: already_isolated | created | work_in_place | blockedbaseline_commandsbaseline_resultnext_ownerUse 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.