apex

Coordinate end-to-end software changes using the APEX Analyze-Plan-Execute-eXamine methodology.

2|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/coroboros/agent-skills --skill apex-coroboros
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apex
Source: https://github.com/coroboros/agent-skills/tree/main/skills/apex
Command: npx skills add https://github.com/coroboros/agent-skills --skill apex-coroboros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

APEX provides a structured, repeatable workflow to plan, implement, and validate software tasks using the Analyze-Plan-Execute-eXamine (APEX) methodology, increasing clarity and auditability while reducing cognitive load.

Core Features & Use Cases

  • End-to-end workflow for non-trivial features, bug fixes, or refactors across multiple files with progressive step loading.
  • Optional economy mode to reduce token usage by avoiding subagents and using direct tooling.
  • Save-and-resume capability with template-based outputs to persist state and resume work later.

Quick Start

Run the APEX flow to analyze, plan, execute, and eXamine code changes with progressive templates.

Frequently Asked Questions about apex

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

FAQPage Schema
How do I coordinate end-to-end feature implementation across multiple files?

Feature implementation across multiple files is coordinated using the APEX methodology—Analyze, Plan, Execute, and eXamine—to ensure systematic, auditable software work with progressive step loading.

What is the APEX workflow for software planning and validation?

The APEX workflow is a structured methodology that systematically analyzes, plans, executes, and examines code changes. It uses progressive templates and stateful outputs to minimize token usage while preserving deterministic execution and traceability.

How do I reduce token usage when automating codebase refactoring tasks?

Token usage during codebase refactoring is reduced by enabling economy mode, which avoids parallel subagents and uses direct tooling, alongside progressive step loading to manage context efficiently.

Can I save and resume a multi-file feature workflow later?

Yes, the feature workflow supports save-and-resume capabilities using template-based outputs, which persist the current state and allow you to resume non-trivial software tasks at a later time.

Does the APEX methodology require parallel subagents for bug fixes?

No, parallel subagents are optional for bug fixes. The methodology supports an economy mode that bypasses subagents and uses direct tooling to execute changes while maintaining deterministic, traceable outputs.

When should I use a systematic planning workflow for unfamiliar codebases?

A systematic planning workflow should be used for non-trivial changes in unfamiliar codebases, including bug fixes, feature additions, and refactors, to reduce cognitive load and ensure auditable, traceable execution.