workflow

Execute structured multi-phase agent workflows with evidence-based gates.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/vexjoy-agent --skill workflow-notque
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/notque/vexjoy-agent/tree/main/skills/workflow
Command: npx skills add https://github.com/notque/vexjoy-agent --skill workflow-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents ad-hoc, skip-step agent behavior by forcing structured multi-phase execution (review, debug, refactor, research, deploy) with explicit methodology and evidence-based gates.

Core Features & Use Cases

  • Workflow Reference Routing: Selects the correct workflow reference from an indexed library, then follows its phases and output format exactly.
  • Evidence-First Execution: Uses gate-driven workflows where verification is required before completion.
  • Multi-Phase Methodology: Supports end-to-end phased lifecycles like code review, systematic debugging, safe refactoring, research pipelines, and PR workflows.
  • Cleanup/Tidy Refactor Support: Includes refactor workflows intended to improve structure without changing behavior.

Quick Start

Use the workflow skill to run a structured multi-phase process by asking for a workflow like “tidy up this repo without changing behavior,” and ensure it follows the matching reference phases and gate outputs.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I run a structured multi-phase code review with evidence-based gates?

A structured code review uses gate-driven workflows to enforce evidence-based verification before completion. It prevents ad-hoc agent behavior by loading a specific reference file and executing phases in exact order without improvising.

What is the best way to tidy up a repository without changing its behavior?

Tidy up a repository without changing behavior by using a dedicated safe refactoring workflow. This process applies cleanup-specific phases and evidence-based gates defined in the workflow reference to improve code structure systematically.

How does systematic debugging work in a phased pipeline?

Systematic debugging in a phased pipeline forces agents to follow reference-defined execution steps rather than skipping ahead. It requires passing evidence-based gates at each phase boundary to isolate and resolve issues methodically.

Can I use workflow orchestration for end-to-end research pipelines?

Yes, you can use workflow orchestration for end-to-end research pipelines. The system supports multi-phase methodology by routing to the correct research reference and executing its phases sequentially with required gate verification.

Does multi-phase execution prevent agents from improvising during refactoring?

Yes, multi-phase execution prevents improvising during refactoring by requiring agents to load a reference file and follow its exact phases. This structured approach stops skip-step behavior and enforces safe refactoring through evidence-based gates.