execute
Carry an approved task through to working, verified code
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 786fc2e9997ff4d2… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Execute
Use this skill when the work is understood and the job is to build it.
This is the canonical execution workflow. autopilot, ralph, ultragoal,
ultrapilot, pipeline, and swarm route here.
Goal
Take a task from agreed intent to working code, with evidence that it works.
Workflow
- Confirm the task is clear enough to build. If it is not, plan first.
- Break the work into independent units; run genuinely independent units in parallel.
- Implement the smallest correct change per unit, reusing existing utilities and patterns.
- Verify as you go, not only at the end.
- Report what changed, what was verified, and what remains.
Scale
Match the machinery to the task:
- Single unit — implement directly, verify, done.
- Several independent units — delegate to
executoragents in parallel. - Long-running or unbounded — keep a durable task list and continue until the list is empty.
- Needs coordinated parallel workers — use
team.
Do not spin up coordination for work that one focused pass would finish.
Rules
- Prefer deletion over addition when behavior is preserved.
- Do not add dependencies without an explicit request.
- Keep diffs small and reversible.
- Placeholder TODOs,
test.skip, and stub tests are blockers, not progress. - Authoring and approval are separate passes — do not self-approve; hand off to
revieworverify.
Completion
Before claiming done:
- No pending tasks
- Tests pass, or failures are reported plainly
- Verification evidence collected
Output
- Files changed
- What was implemented
- Evidence it works
- What is still open
Files
1- SKILL.md
7d7fdc3be11.7 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from Yeachan-Heo/oh-my-claudecode8
Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 se
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Periodic architecture survey — walks the module graph and reports ranked deepening candidates (shallow modules, hypothetical seams, logic behind the wrong seam). Survey, not rescue: it finds candidates and hands them to the captain; it never refactors on its own.
Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding,
Full autonomous execution from idea to working code
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior
Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state