/execute

name: wrap:execute
description: Load phase-relevant skills before GSD execute-phase, then capture execution observations
argument-hint: "[phase-number]"
allowed-tools:
  - Read
  - Write
  - Bash
  - Glob
  - Task

/wrap:execute -- Skill-enhanced GSD execute-phase

<objective> Wrap GSD execute-phase with automatic skill loading before execution and observation capture after completion. The user runs `/wrap:execute N` where N is the phase number. This command:

1. Reads integration config to check if wrappers are enabled 2. Loads phase-relevant skills based on the phase domain/topic 3. Delegates to the real GSD execute-phase command (never reimplements GSD logic) 4. Captures execution observations to sessions.jsonl for pattern detection 5. Displays a transparency summary of what was loaded and captured

If skill loading or observation capture fails at any point, the GSD command still runs normally. The wrapper enhances but never blocks. </objective>

<companion-skills> As the **first step in handler dispatch** (before Step 2 skill loading), invoke the `intent-router` skill to classify the request's information-need and return a strategy label, a token budget, and a retrieval depth. Use that to specialise downstream skill loading rather than defaulting one retriever for everything. Advisory and best-effort: if intent-router is unavailable, proceed with the default loading path (the wrapper never blocks). </companion-skills>

<process>

Step 0: Parse Arguments

Extract the phase number N from the user's input.

• If the user provided a number (e.g., `/wrap:execute 5`), use that as N.
• If no phase number was provided, read `.planning/STATE.md` using the Read tool and extract the current phase number from the `Phase:` line under `## Current Position`.
• If STATE.md does not exist and no phase number was given, ask the user to specify one: "No phase number provided and STATE.md not found. Please run `/wrap:execute N` with a phase number."

Store N for use in all subsequent steps.

---

Step 1: Read Integration Config (WRAP-05)

Read `.planning/skill-creator.json` using the Read tool.

**If the file does not exist:** Proceed with all features enabled. This follows the opt-out model: everything defaults to `true`.

• `wrapper_commands`: true (default)
• `auto_load_skills`: true (default)
• `observe_sessions`: true (default)

**If the file exists, parse it and extract:**

• `integration.wrapper_commands` -- the master toggle for all wrapper commands
• `integration.auto_load_skills` -- controls whether skills are loaded in Step 2
• `integration.observe_sessions` -- controls whether observations are captured in Step 4

**If `integration.wrapper_commands` is explicitly `false`:** Display the following message and stop:

Wrapper commands are disabled in `.planning/skill-creator.json`.
Run `/gsd:execute-phase N` directly, or enable wrappers by setting
`integration.wrapper_commands` to `true` in the config.

Do not proceed to further steps.

**If parsing fails** (malformed JSON, unexpected structure), log the error and proceed with defaults.

---

Step 2: Load Phase-Relevant Skills (WRAP-06 graceful degradation)

**This entire step is wrapped in error handling.** If ANY part of skill loading fails -- file read errors, glob failures, parsing problems -- log the failure and proceed directly to Step 3. Skill loading must never block GSD execution.

**If `integration.auto_load_skills` is `false`**, skip this step and display:

Skill loading disabled in config. Proceeding with base GSD execution.

**If enabled (default):**

2a. Extract phase domain

Read `.planning/ROADMAP.md` using the Read tool. Find the entry for Phase N and extract:

• The phase name/title
• The phase goal or description text
• Any requirement IDs or domain keywords

Determine the phase topic/domain from the goal text. Look for keywords such as: "auth", "authentication", "UI", "interface", "API", "endpoint", "test", "testing", "config", "configuration", "database", "schema", "security", "monitoring", "deploy", "CI", "hook", "git", "skill", "pattern", "observation", "wrapper", "command", "install", "validate".

2b. Scan for matching skills

1. Use the Glob tool to find `*.md` files in `.claude/commands/` 2. Use the Glob tool to find `*/SKILL.md` files in `.claude/skills/` 3. For each skill file found, read its first 10 lines to extract frontmatter (name, description) 4. Match skills whose description or name contains keywords from the phase domain 5. Always include skills tagged as always-applicable (e.g., `beautiful-commits`) regardless of domain match

2c. Display loaded skills (WRAP-07 transparency)

Display which skills were loaded:

### Skills Loaded
- beautiful-commits (always-applicable)
- tdd-workflow (matches phase topic: "testing")
Loaded 2 skills for Phase N execution.

If no skills match the phase domain, display:

### Skills Loaded
No phase-specific skills found. Proceeding with base GSD execution.

If skill scanning encounters an error at any point, display:

### Skills Loaded
Skill loading encountered an error. Proceeding without skill enhancement.

---

Step 3: Delegate to GSD execute-phase

This is the core step. The wrapper invokes the real GSD command -- it does NOT reimplement any GSD logic.

1. Read the file `.claude/commands/gsd/execute-phase.md` using the Read tool 2. **If the file exists:** Follow its instructions with phase number N as the argument. Execute the full GSD execute-phase process as documented in that command file. 3. **If the file does NOT exist** (GSD commands stored elsewhere): Use the Task tool to invoke. Pass an `effort` parameter derived from the current GSD profile (`/gsd:set-profile`): `quality`→`high`, `balanced`→`medium`, `budget`→`low`. Omit `effort` for `inherit` to preserve the parent runtime's default behavior (OGA-016, additive). Source the profile from `.planning/skill-creator.json` `integration.profile`.