skills.rest
fusengine
fusengineCOMMUNITY
Explore all skills by this author →
Website𝕏@fusengineGitHub

APEX Methodology

Implement software development tasks through Analyze, Plan, Execute, eLicit, and eXamine phases.

22|3|Updated Jan 10, 2026
Search Tags:#code quality#workflow#tdd#development process#solid principles#apex
One-click install
npx skills add https://github.com/fusengine/agents --skill apex-methodology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: APEX Methodology
Source: https://github.com/fusengine/agents/tree/main/plugins/ai-pilot/skills/apex
Command: npx skills add https://github.com/fusengine/agents --skill apex-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic, end-to-end development workflow to ensure code quality, adherence to best practices, and efficient task completion.

Core Features & Use Cases

  • Structured Workflow: Guides you through Analyze → Plan → Execute → eLicit → eXamine phases.
  • TDD Enforcement: Integrates the RED-GREEN-REFACTOR cycle into the Execute phase.
  • Quality Gates: Enforces file size limits, SOLID principles, and expert self-review.
  • Use Case: Use this Skill for any development task, from implementing new features to fixing bugs, ensuring a consistent and high-quality outcome every time.

Quick Start

Follow the APEX workflow to implement the new user authentication feature.

Frequently Asked Questions about APEX Methodology

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

FAQPage Schema
What is a systematic development workflow for ensuring code quality and TDD adherence?▼

A systematic development workflow ensures code quality by guiding tasks through Analyze, Plan, Execute, eLicit, and eXamine phases. It enforces TDD, SOLID principles, and file size limits during software development to guarantee consistent outcomes.

How do I implement test-driven development into my software development process?▼

To implement test-driven development, integrate the RED-GREEN-REFACTOR cycle into the Execute phase of your workflow. This ensures tests are written and validated before code is finalized, maintaining strict development process standards.

Does this development workflow support framework-specific references for different project types?▼

Yes, the development workflow supports various project types by auto-detecting framework-specific references. This allows the process to adapt its quality gates and TDD enforcement to your specific software engineering environment.

What's the best way to structure a software development task from analysis to code review?▼

The best way to structure a development task is using a five-phase workflow: Analyze, Plan, Execute, eLicit, and eXamine. This enforces SOLID principles, file size limits, and expert self-review for high-quality code delivery.

When do I need a structured workflow with quality gates for software engineering?▼

You need a structured workflow with quality gates when implementing new features or fixing bugs to ensure adherence to best practices. It prevents code bloat by enforcing file size limits and SOLID principles during development.

Why does my development process lack consistent code quality and adherence to SOLID principles?▼

Your development process lacks consistent code quality without a systematic workflow enforcing SOLID principles and expert self-review. Implementing a structured phases approach with quality gates ensures high-quality task completion.

Related Skills

Explore More Software Engineering Skills→
nist0nist0

cli-platform-bootstrap

Automates CoDev framework setup in .NET CLI platform repositories.

Community
Intermediate
twikustwikus
3

apex

Automate software delivery using the APEX Analyze-Plan-Execute-Examine methodology.

Community
Advanced
synaptiaisynaptiai
6

tdd-patterns

Track RED-GREEN-REFACTOR tasks for TDD cycles in CI workflows.

Official
Intermediate
joegoldinjoegoldin
2

systematic-debugging

Apply a 4-phase debugging process for root cause analysis and hypothesis testing.

Community
Advanced