Name: omg-autopilot
Author: zereight

Imported from zereight/gitlab-mcp (.github/skills/omg-autopilot/SKILL.md). Install upstream with npx skills add zereight/gitlab-mcp --skill omg-autopilot. Copyright stays with the author.

OMG Autopilot

OMG Autopilot takes a brief product idea and autonomously handles the full lifecycle: requirements analysis, technical design, planning, parallel implementation, QA cycling, and multi-perspective validation.

When to Use

User wants end-to-end autonomous execution from an idea to working code
Task requires multiple phases: planning, coding, testing, and validation
User wants hands-off execution

When NOT to Use

User wants to explore options → use /plan
Single focused code change → use /ralph or delegate to @executor
Quick fix or small bug → delegate directly to @executor

Execution Pipeline

Phase 0 - Expansion

Turn the user's idea into a detailed spec.

If ralplan consensus plan exists (.omc/plans/ralplan-*.md): Skip Phase 0 AND Phase 1 → jump to Phase 2
If deep-interview spec exists (.omc/specs/deep-interview-*.md): Use pre-validated spec, skip to Phase 1
If input is vague: Offer redirect to /deep-interview for clarification
Otherwise: @analyst extracts requirements, @architect creates technical specification
Output: .omc/autopilot/spec.md
Track phase: omg_write_state(phase="expansion_done")

Phase 1 - Planning

Create an implementation plan from the spec.

@architect creates plan (direct mode)
@critic validates plan
Output: .omc/plans/autopilot-impl.md
Track: omg_write_state(phase="planning_done")

Phase 2 - Execution

Implement the plan using parallel execution.

Route tasks by complexity to @executor
Run independent tasks in parallel
Track: omg_write_state(phase="execution_done")

Phase 3 - QA

Cycle until all tests pass (max 5 cycles).

Build, lint, test, fix failures
Stop early if the same error repeats 3 times (fundamental issue)
Track: omg_write_state(phase="qa_done")

Phase 4 - Validation

Multi-perspective review in parallel.

@architect: Functional completeness
@security-reviewer: Vulnerability check
@code-reviewer: Quality review
All must approve; fix and re-validate on rejection
Track: omg_write_state(phase="validation_done")

Phase 5 - Cleanup

Delete all state files on successful completion.

Run /cancel for clean exit

Stop Conditions

Same QA error persists across 3 cycles → report fundamental issue
Validation keeps failing after 3 rounds → report issues
User says "stop", "cancel", or "abort"

Checklist

Install omg-autopilot and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zereight-gitlab-mcp-omg-autopilot", "kind": "skill", "name": "omg-autopilot", "description": "Full autonomous execution from idea to working code. Activate when user says: autopilot, auto-pilot, autonomous, build me, create me, make me, full auto, handle it all, or \"I want a/an...\"", "publisher": "zereight", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Full autonomous execution from idea to working code. Activate when user says: autopilot, auto-pilot, autonomous, build me, create me, make me, full auto, handle it all, or \"I want a/an...\"" ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/zereight/gitlab-mcp", "path": ".github/skills/omg-autopilot/SKILL.md", "ref": "HEAD", "url": "https://github.com/zereight/gitlab-mcp/blob/HEAD/.github/skills/omg-autopilot/SKILL.md", "key": "zereight/gitlab-mcp/.github/skills/omg-autopilot/SKILL.md" } }, "instructions": "# OMG Autopilot\n\nOMG Autopilot takes a brief product idea and autonomously handles the full lifecycle: requirements analysis, technical design, planning, parallel implementation, QA cycling, and multi-perspective validation.\n\n## When to Use\n- User wants end-to-end autonomous execution from an idea to working code\n- Task requires multiple phases: planning, coding, testing, and validation\n- User wants hands-off execution\n\n## When NOT to Use\n- User wants to explore options → use `/plan`\n- Single focused code change → use `/ralph` or delegate to @executor\n- Quick fix or small bug → delegate direct", "cost": { "context_tokens": 639 } }

omg-autopilot

About