lp-implement

Execute LittlePea delivery loop from implement through QA after plan approval.

Updated Apr 14, 2026

Search Tags:#workflow #execution #orchestrator #qa-automation #plan-approval #delivery-loop

Ready to run

npx skills add https://github.com/daudaudinang/vibecode --skill lp-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lp-implement
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/lp-implement
Command: npx skills add https://github.com/daudaudinang/vibecode --skill lp-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical LittlePea delivery-loop execution from plan approval through implement, review, and QA to ensure predictable, governed delivery.

Core Features & Use Cases

Orchestrates the canonical delivery loop: execute implement → review-implement → qa-automation with runtime guards and state synchronization.
Enforces prerequisites and guards: validates plan_approved = true and coordinates gate transitions, artifact syncing, and contract updates.
Supports scalable delivery workflows: handles Epic mode phase naming, error handling, and deterministic progression through the pipeline.

Quick Start

Activate this skill after a plan is approved to run the end-to-end delivery loop from implement through QA.

Frequently Asked Questions about lp-implement

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

FAQPage Schema

How do I automate the delivery loop from implementation to QA after plan approval?▼

To automate the delivery loop after plan approval, use an orchestrator-backed workflow to execute implement, review, and qa-automation phases. It validates that plan_approved equals true, coordinates state gates, and outputs artifacts to .codex/pipeline.

What are the prerequisites for running an automated delivery loop with state synchronization?▼

Running an automated delivery loop requires an orchestrator-backed workflow with the plan_approved state set to true. The pipeline enforces these prerequisites to coordinate gate transitions and contract syncing before executing implementation phases.

How does the delivery orchestrator handle contract syncing and state gates during execution?▼

The delivery orchestrator handles contract syncing and state gates by validating prerequisites, coordinating deterministic progression through implementation and review, and synchronizing artifacts under .codex/plans and .codex/pipeline directories.

Can I use Epic mode phase naming within an automated QA and implementation workflow?▼

Yes, you can use Epic mode phase naming within the automated QA and implementation workflow. The delivery loop supports Epic mode naming alongside error handling and deterministic pipeline progression to scale delivery operations.

What happens if plan_approved is not true when starting the delivery loop?▼

If plan_approved is not true, the delivery loop enforces its prerequisite guards and halts execution. The orchestrator requires this validated state to coordinate gate transitions and artifact syncing before running implementation.

Where are pipeline artifacts stored after executing an automated delivery loop?▼

Pipeline artifacts are stored under the .codex/pipeline and .codex/plans directories after executing the delivery loop. The orchestrator produces these outputs while syncing contracts and transitioning state gates.