pev-cycle

Coordinate plan-execute-validate cycles for Cortex-backed software changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ddpoe/pev-agent-nexus --skill pev-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pev-cycle
Source: https://github.com/ddpoe/pev-agent-nexus/tree/main/plugins/pev/skills/pev-cycle
Command: npx skills add https://github.com/ddpoe/pev-agent-nexus --skill pev-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate and coordinate complex, multi-party software changes by managing a cyclic workflow that splits work into planning, building, reviewing, and auditing stages.

Core Features & Use Cases

  • Orchestrates a Plan-Execute-Validate cycle by dispatching subagents (Architect, Builder, Reviewer, Auditor) to implement changes through a repeatable process.
  • Supports staged work in a Cortex-backed environment with worktrees and manifests, enabling traceable changes and rollback if needed.
  • Real-world use: teams implementing architectural changes, feature toggles, or refactors can run end-to-end cycles with governance and quality checks.

Quick Start

Start a PEV cycle by initiating a cycle request using the plugin's orchestrator in your CLI or UI.

Frequently Asked Questions about pev-cycle

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

FAQPage Schema
How do I automate plan-execute-validate workflows for software engineering teams?

Automate plan-execute-validate workflows by orchestrating a cyclic process that dispatches subagents through planning, building, reviewing, and auditing stages for complex multi-party software changes.

What is a PEV cycle and how does it manage architectural changes?

A PEV cycle is a deterministic phase flow that coordinates end-to-end architectural changes by splitting work into plan, build, review, and audit stages with cycle manifests and robust state management.

Does this orchestration workflow support Cortex-backed worktrees for traceable deployments?

Yes, the orchestration workflow supports staged work in a Cortex-backed environment with worktrees and manifests, enabling traceable feature deployments and rollback if needed.

How do I start a PEV cycle for feature toggles and governance checks?

Start a PEV cycle for feature toggles by initiating a cycle request using the orchestrator in your CLI or UI to run end-to-end cycles with governance and quality checks.

What is the best way to orchestrate multi-party software refactors with error handling?

The best way to orchestrate multi-party refactors is using a deterministic phase flow that dispatches subagents for each stage, providing robust state management, cycle manifests, and error handling.

When should I not use a cyclic workflow for software deployments?

You should avoid a cyclic workflow for simple, single-step modifications that do not require multi-party coordination, staged reviews, or governance audits across separate subagents.