lp-pipeline-orchestrator

Orchestrate LP workflows by coordinating worker skills with SQLite-backed state.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/daudaudinang/vibecode --skill lp-pipeline-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lp-pipeline-orchestrator
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/lp-pipeline-orchestrator
Command: npx skills add https://github.com/daudaudinang/vibecode --skill lp-pipeline-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It provides a single source of truth for orchestrating the /lp:* namespace, coordinating worker skills and a SQLite-backed state manager to ensure consistent execution and state reconciliation.

Core Features & Use Cases

  • Orchestrates worker skills according to a state machine to drive spec/plan/implement cycles.
  • Enforces canonical artifact layout under .codex, gates, and retry policies to maintain reliability.
  • Syncs machine contracts into the state for accurate resume and recovery across restarts.

Quick Start

Start the orchestrator in your project workspace and begin the /lp workflow sequence.

Frequently Asked Questions about lp-pipeline-orchestrator

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

FAQPage Schema
How does SQLite-backed workflow orchestration help manage software development state?

The orchestrator coordinates worker skills through a state machine to drive spec, plan, and implement cycles. It enforces a canonical .codex artifact layout, gates, and retry policies to maintain execution reliability across the entire lifecycle.

How do I coordinate spec and plan delivery cycles for end-to-end workflows?

The orchestrator enforces a canonical .codex artifact layout with robust gatekeeping and retry policies. It manages artifacts across spec, plan, implement, review, cook, and debug phases to maintain consistent execution and state reconciliation.

Can I resume an interrupted state machine workflow after a failure?

The orchestrator applies a unified decision model and retry policies to resume work after failures. It uses a SQLite-backed state to ensure consistent execution and state reconciliation across the /lp:* namespace.

What is the best way to enforce artifact layout and gates during code implementation?

This orchestrator uses a SQLite-backed state manager to provide a single source of truth for the /lp:* namespace. It coordinates worker skills and enforces canonical layouts, gates, and retry policies for consistent execution.

Do I need external dependencies to run a SQLite-backed state machine for workflow planning?

No, you do not need external dependencies to run this SQLite-backed state machine. The orchestrator operates independently with scripts and references to manage state reconciliation and workflow planning without external packages.

Why does workflow orchestration fail to maintain consistent execution across restarts?

Workflow orchestration fails across restarts when lacking a unified decision model and persistent state. This orchestrator solves it by syncing machine contracts into SQLite, enforcing gates, and applying retry policies for accurate recovery.