execute

Orchestrate the full APEX workflow from research to ship in one session.

3|1|Updated Jul 2, 2025
One-click install
npx skills add https://github.com/benredmond/apex --skill execute-benredmond
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/benredmond/apex/tree/main/skills_backup/20260112-223111/skills/execute
Command: npx skills add https://github.com/benredmond/apex --skill execute-benredmond

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the full APEX workflow (research → plan → implement → ship) in a single session to eliminate context switching and ensure end-to-end delivery.

Core Features & Use Cases

  • End-to-end automation: runs all four phases in sequence for a single task.
  • Identifier propagation: passes a task identifier across phases with verification.
  • Suitable for single-session tasks: when you want complete workflow without manual skill invocation.

Quick Start

Example: /apex:execute "add user authentication"

Frequently Asked Questions about execute

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

FAQPage Schema
How do I automate a full development workflow from research to shipping in one session?

Automating a full development workflow in one session requires orchestrating research, planning, implementation, and shipping phases sequentially without context switching. This approach coordinates phase transitions and passes a task identifier across all stages to verify artifacts and ensure end-to-end delivery.

What is the APEX workflow and how does single-session task orchestration work?

The APEX workflow is a structured task management process spanning research, plan, implement, and ship phases. Single-session orchestration works by running all four phases in sequence for one task, passing an identifier across phases, and verifying completion status to eliminate manual phase invocation.

Can I run the full APEX workflow for large or complex development tasks?

Running the full APEX workflow in a single session is suitable for small-to-medium tasks that can be completed without pauses between phases. Large or complex tasks requiring breaks between research, planning, implementation, and shipping phases are not ideal for this single-session orchestration approach.

How do I start end-to-end workflow automation for a single coding task?

To start end-to-end workflow automation, invoke the execute command with a quoted task description like adding a feature. This triggers the full APEX sequence—research, plan, implement, ship—automatically coordinating transitions and verifying artifacts such as task files for that specific identifier.

Why does task workflow automation require passing an identifier across phases?

Task workflow automation requires passing an identifier across phases to maintain continuity and verify artifacts like task files and completion status. This identifier propagation ensures that research, planning, implementation, and shipping stages stay coordinated within the same single-session context.

What are the limitations of running the research to ship workflow without context switching?

The main limitation of running the research to ship workflow without context switching is that it only applies to small-to-medium tasks completable in one session. Tasks requiring pauses between phases, manual intervention, or extended deliberation are not suited for this automated single-session orchestration.