execute

Execute one sub-task with implementation, verification, and commit in Linear or Jira.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MediTracer/mobius --skill execute-meditracer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/MediTracer/mobius/tree/main/.opencode/skills/execute
Command: npx skills add https://github.com/MediTracer/mobius --skill execute-meditracer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the execution of a single sub-task within a larger issue workflow, ensuring a bounded, context-primed operation and stopping after one sub-task completes so the loop can safely continue with the next item.

Core Features & Use Cases

  • Execute exactly one sub-task per invocation, with complete isolation from other tasks.
  • Load the parent issue and the next ready sub-task, check blockers, and mark the sub-task as In Progress.
  • Implement changes, run verification (typecheck, tests, lint), commit, and update local context, then report completion and stop so the loop can invoke the next sub-task.

Quick Start

Run /execute with a parent or sub-task ID to begin processing the next sub-task; the loop will call this skill again for subsequent tasks.

Frequently Asked Questions about execute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute a single sub-task from a larger issue automatically?

To execute a single sub-task, this skill loads the parent issue, checks blockers, and marks the sub-task as in progress before implementing changes, verifying, and committing. It processes exactly one sub-task per invocation and stops to await the next cycle.

How does the Mobius orchestration loop handle parallel agents without race conditions?

The Mobius orchestration loop supports parallel agents by executing exactly one isolated sub-task per invocation, priming context and stopping after commit to prevent race conditions. Each agent operates on a distinct sub-task within the structured workflow loop.

Can I use this sub-task execution workflow with Jira and Linear environments?

Yes, this sub-task execution workflow applies in both Linear and Jira environments. It integrates with these platforms through the Mobius orchestration loop to load parent issues, mark sub-tasks in progress, and update structured outputs.

What is the best way to automate issue verification and commits for individual sub-tasks?

Automating issue verification and commits for individual sub-tasks requires loading the next ready sub-task, implementing changes, running typecheck, tests, and lint, then committing. This skill bounds the operation to one sub-task and reports completion for the loop.

Do I need a valid sub-task context to start the workflow execution?

Yes, a valid sub-task context is required to start the workflow execution. Requirements include a valid sub-task context, in-progress marking, and structured output for the orchestration loop to safely continue with the next item.