Execute LittlePea delivery loop from implement through QA after plan approval.
npx skills add https://github.com/daudaudinang/vibecode --skill lp-implement
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
Canonical LittlePea delivery-loop execution from plan approval through implement, review, and QA to ensure predictable, governed delivery.
Activate this skill after a plan is approved to run the end-to-end delivery loop from implement through QA.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
yiwei79Orchestrate Azoth's /deliver-full workflow with governance gates and kernel-level checks.
YunosukeYoshinoVerify quality gates and artifacts before generating a PR summary and Codex review request.
GrinRusDefine and enforce shared output, read, and loop-safety policies across AIDD stages.
d-padmanabhanGuide AI coding agents through Plan, Implement, and Review phases with approval gates.
