pev-builder

Translate architect pitches into tasks and maintain a cycle manifest in isolated worktrees.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the Planner-to-Execution transition in Plan-Execute-Validate cycles by providing a deterministic Builder workflow that reads pitches, decomposes work, and returns a manifest for review.

Core Features & Use Cases

  • Translates Architect pitches into executable tasks suitable for a Git-based worktree.
  • Supports test-driven development and structured progress recording in the cycle manifest.
  • Enables auditable builds by committing changes in a separate worktree and presenting a final implementation manifest.

Quick Start

Coordinate the Builder phase by translating pitches into tasks, implementing with TDD, and returning a structured manifest.

Frequently Asked Questions about pev-builder

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

FAQPage Schema
How do I automate translating architect pitches into actionable git workflow tasks?

To automate translating architect pitches into git workflow tasks, you can use a deterministic Builder workflow that reads the pitch, decomposes the work, and generates an actionable implementation manifest for review.

What is the best way to enforce test-driven development during automated project execution?

The best way to enforce test-driven development during automated project execution is by applying a Builder workflow that structures task-oriented TDD and records structured progress within a cycle manifest.

How do I isolate code changes in an automated build cycle for safer review?

You can isolate code changes in an automated build cycle by implementing features in a separate git-based worktree, committing the results, and returning a final verifiable implementation manifest for review.

Can I maintain a deterministic cycle manifest for Plan-Execute-Validate builds?

Yes, you can maintain a deterministic cycle manifest for Plan-Execute-Validate builds by enforcing structured progress recording and updating the manifest throughout the isolated worktree coding and git commit process.

Does automated workflow execution require manual intervention between planning and coding phases?

Automated workflow execution does not require manual intervention between planning and coding phases because the Builder phase autonomously translates pitches into tasks and executes them within an isolated worktree before returning a manifest.

What are the limitations of relying on a cycle manifest for project execution verification?

Relying on a cycle manifest for project execution verification limits real-time intervention, as the workflow operates autonomously within an isolated worktree and only returns results for review after the final git commit.