---
name: Execute
slug: execute-2
category: Automation
description: Execute is used when a task is implementation-ready and needs code changes now. It guides the agent to confirm scope, edit the smallest necessary files, run checks, and report validation and follow-ups.
github: "https://github.com/Joonghyun-Lee-Frieren/oh-my-antigravity/tree/main/skills/execute"
language: JavaScript
stars: 210
forks: 27
install: "npx degit https://github.com/Joonghyun-Lee-Frieren/oh-my-antigravity/tree/main/skills/execute ~/.claude/skills/execute"
installs_to: ~/.claude/skills/execute
source_path: skills/execute/SKILL.md
collection_size: 11
category_size: 1860
collection_url: "https://dirskills.com/collections/Joonghyun-Lee-Frieren/oh-my-antigravity"
added: 2026-09-04T05:26:21.217Z
last_synced: 2026-09-04T05:26:21.217Z
canonical_url: "https://dirskills.com/skills/execute-2"
---

# Execute

Execute is used when a task is implementation-ready and needs code changes now. It guides the agent to confirm scope, edit the smallest necessary files, run checks, and report validation and follow-ups.

**Install:**

```bash
npx degit https://github.com/Joonghyun-Lee-Frieren/oh-my-antigravity/tree/main/skills/execute ~/.claude/skills/execute
```

## README

## Purpose

Use this skill when the task is implementation-ready and requires code changes now.

## Trigger

- User asks to implement, refactor, or fix code directly
- A plan already exists and a specific phase is selected

## Workflow

1. Confirm exact scope and acceptance criteria.
2. Read target files and lane/task state before editing.
3. Load only relevant files and preserve existing conventions.
4. Implement the smallest viable diff.
5. Prefer editing existing files over creating new files unless scope requires it.
6. Run the most relevant checks/tests.
7. Summarize changed files, validation, blockers, and remaining work.

## Output Template

```markdown
## Scope
- ...

## Files Changed
- ...

## Validation
- ...

## Blockers
- ...

## Follow-ups
- ...
```

## Notes

- Escalate to `oma-reviewer` for high-risk or cross-cutting changes.
- Use `oma-debugger` immediately when checks fail.
- If permissions/tools are denied, stop and return explicit approval/fallback needs.