How do I install the Execute Setup skill?

Run npx skillmds@latest add samuel-venturin/execute-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Execute Setup skill do?

Create or locate worktree for task execution. Step 4 of execute workflow. It is listed under Productivity on SkillMD.

Is Execute Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Execute Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Execute Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Execute Setup?

samuel-venturin (@samuel-venturin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Execute Setup by samuel-venturin — Agent Skill

Name: Execute Setup
Author: samuel-venturin

File contents

/execute-setup — Worktree Setup Phase

$TM = python3 ~/.claude/scripts/task_manager.py

Input (from /execute-validate output):

$TICKET — validated ticket ID
$PROJECT_ROOT — project root directory

Step 4 — WORKTREE_GUARD

Locate the worktree:

WORKTREE_PATH=../<PROJECT_ROOT_BASENAME>-worktrees/<TICKET>

If worktree exists:

Display status:

"✅ Worktree encontrada: <WORKTREE_PATH>"

Always sync runtime/config files from project root:

mkdir -p $WORKTREE_PATH/public $WORKTREE_PATH/e2e
[ -f <PROJECT_ROOT>/.env ] && cp <PROJECT_ROOT>/.env $WORKTREE_PATH/.env
[ -f <PROJECT_ROOT>/public/config.json ] && cp <PROJECT_ROOT>/public/config.json $WORKTREE_PATH/public/config.json
[ -f <PROJECT_ROOT>/.npmrc ] && cp <PROJECT_ROOT>/.npmrc $WORKTREE_PATH/.npmrc
[ -f <PROJECT_ROOT>/e2e/.env.e2e ] && cp <PROJECT_ROOT>/e2e/.env.e2e $WORKTREE_PATH/e2e/.env.e2e

Proceed to next phase.

If worktree does not exist:

Warn:

"⚠️ Worktree <WORKTREE_PATH> não encontrada. A worktree deveria ter sido criada pelo /interpret. Criar agora a partir de origin/develop?"

If user confirms:

git fetch origin
git worktree add $WORKTREE_PATH <branch_from_index> origin/develop
mkdir -p $WORKTREE_PATH/public $WORKTREE_PATH/e2e
[ -f <PROJECT_ROOT>/.env ] && cp <PROJECT_ROOT>/.env $WORKTREE_PATH/.env
[ -f <PROJECT_ROOT>/public/config.json ] && cp <PROJECT_ROOT>/public/config.json $WORKTREE_PATH/public/config.json
[ -f <PROJECT_ROOT>/.npmrc ] && cp <PROJECT_ROOT>/.npmrc $WORKTREE_PATH/.npmrc
[ -f <PROJECT_ROOT>/e2e/.env.e2e ] && cp <PROJECT_ROOT>/e2e/.env.e2e $WORKTREE_PATH/e2e/.env.e2e

If user declines:

"⛔ Worktree creation cancelled. Cannot proceed." Stop.

✅ SUCCESS PATH

If worktree exists or was created successfully:

From this point, PROJECT_ROOT = WORKTREE_PATH (for all subsequent operations).

Return setup result:

{
  "ticket": "<TICKET>",
  "setup_passed": true,
  "worktree_path": "<WORKTREE_PATH>",
  "status": "created | existing"
}

Proceed to next phase: /execute-transition (transition to doing)

Safety rules

Never delete or reset existing worktrees without explicit user confirmation.
Always sync .env, public/config.json, .npmrc, and e2e/.env.e2e to maintain environment consistency.

---name: execute-setupdescription: Create or locate worktree for task execution. Step 4 of execute workflow.---# /execute-setup — Worktree Setup Phase> `$TM` = `python3 ~/.claude/scripts/task_manager.py`Input (from `/execute-validate` output):- `$TICKET` — validated ticket ID- `$PROJECT_ROOT` — project root directory---## Step 4 — WORKTREE_GUARDLocate the worktree:```bashWORKTREE_PATH=../<PROJECT_ROOT_BASENAME>-worktrees/<TICKET>```### If worktree **exists**:1. Display status: > "✅ Worktree encontrada: `<WORKTREE_PATH>`"2. Always sync runtime/config files from project root: ```bash mkdir -p $WORKTREE_PATH/public $WORKTREE_PATH/e2e [ -f <PROJECT_ROOT>/.env ] && cp <PROJECT_ROOT>/.env $WORKTREE_PATH/.env [ -f <PROJECT_ROOT>/public/config.json ] && cp <PROJECT_ROOT>/public/config.json $WORKTREE_PATH/public/config.json [ -f <PROJECT_ROOT>/.npmrc ] && cp <PROJECT_ROOT>/.npmrc $WORKTREE_PATH/.npmrc [ -f <PROJECT_ROOT>/e2e/.env.e2e ] && cp <PROJECT_ROOT>/e2e/.env.e2e $WORKTREE_PATH/e2e/.env.e2e ```3. Proceed to next phase.### If worktree **does not exist**:1. Warn: > "⚠️ Worktree `<WORKTREE_PATH>` não encontrada. A worktree deveria ter sido criada pelo `/interpret`. > Criar agora a partir de `origin/develop`?"2. If user confirms: ```bash git fetch origin git worktree add $WORKTREE_PATH <branch_from_index> origin/develop mkdir -p $WORKTREE_PATH/public $WORKTREE_PATH/e2e [ -f <PROJECT_ROOT>/.env ] && cp <PROJECT_ROOT>/.env $WORKTREE_PATH/.env [ -f <PROJECT_ROOT>/public/config.json ] && cp <PROJECT_ROOT>/public/config.json $WORKTREE_PATH/public/config.json [ -f <PROJECT_ROOT>/.npmrc ] && cp <PROJECT_ROOT>/.npmrc $WORKTREE_PATH/.npmrc [ -f <PROJECT_ROOT>/e2e/.env.e2e ] && cp <PROJECT_ROOT>/e2e/.env.e2e $WORKTREE_PATH/e2e/.env.e2e ```3. If user declines: > "⛔ Worktree creation cancelled. Cannot proceed." > **Stop.**---## ✅ SUCCESS PATHIf worktree exists or was created successfully:1. **From this point, `PROJECT_ROOT = WORKTREE_PATH`** (for all subsequent operations).Return setup result:```json{ "ticket": "<TICKET>", "setup_passed": true, "worktree_path": "<WORKTREE_PATH>", "status": "created | existing"}```**Proceed to next phase: `/execute-transition` (transition to `doing`)**---## Safety rules- Never delete or reset existing worktrees without explicit user confirmation.- Always sync `.env`, `public/config.json`, `.npmrc`, and `e2e/.env.e2e` to maintain environment consistency.

Frequently asked questions

Execute Setup