piv

What This Skill Does

The PIV (Plan, Implement, Validate) Orchestrator is a robust workflow manager for OpenClaw designed to transform high-level development requirements into production-ready code. It operates as the master controller for the software development lifecycle, utilizing a multi-agent architecture to manage complex tasks. Unlike standard agents that attempt to do everything in one go, the PIV skill enforces a strict separation of concerns, assigning specialized sub-agents to specific phases: PRD creation, PRP generation, codebase analysis, code execution, and rigorous validation.

The skill intelligently detects your current context—either by pathing directly to a Product Requirements Document (PRD) or by initializing a project workspace—and ensures the correct directory structure is established. It maintains the system's focus by acting as a lean 'Orchestrator,' spawning fresh, dedicated sub-agents for each phase to prevent context saturation and ensure high-quality, iterative output.

Installation

To add this skill to your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/smokealot420/piv

Once installed, ensure your project directory has a PRDs folder to hold your requirement documents. The skill will automatically handle the setup of your PRPs and templates directories upon first initialization.

Use Cases

• Complex Feature Development: Breaking down large features into discrete, testable phases.
• Automated Refactoring: Managing systematic codebase updates where validation is required after every transformation.
• Multi-Agent Orchestration: Coordinating specialized coding, testing, and documentation agents to maintain project consistency.
• Standardized Dev Ops: Enforcing a consistent documentation-to-code pipeline across multiple team members.

Example Prompts

1. "@piv start development on the new user authentication module located at ./PRDs/auth-module.md starting from phase 1."
2. "@piv /home/dev/projects/api-service 2 4 - resume working on the api-service, jumping straight to phase 2 through 4."
3. "@piv init /projects/new-dashboard - setup the necessary project folder structure for a new feature project."

Tips & Limitations

• Context Hygiene: The Orchestrator enforces a 15% orchestrator/100% sub-agent context rule. Avoid stuffing the orchestrator with too much raw data; pass it through the PRD instead.
• Validation First: Always ensure your piv-validator.md instructions are clear; the orchestrator will not proceed if the validator fails the previous phase.
• PRD Dependency: This skill is strictly opinionated regarding PRDs. Without a well-defined PRD, the orchestrator will halt to prevent hallucinated logic.
• Manual Intervention: While the loop is automated, always review the generated PRPs before triggering the executor if you are working on critical production infrastructure.