lp-plan

Create a canonical LittlePea plan and pause at the human gate.

Updated Apr 14, 2026

Search Tags:#workflow #planning #orchestration #plan-review #human-gate #lp-pipeline

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical LittlePea planning entrypoint that creates a reviewed plan and stops at a human gate, ensuring planning work aligns with business goals before implementation.

Core Features & Use Cases

Plan creation and review: generate a canonical plan for a given feature or requirement, then pause at human gate.
Spec-driven planning: if a spec exists, align the plan to the spec as the source of truth.
Orchestrated state and artifacts: produce plan artifacts and sync plan state through the pipeline while gating execution.

Quick Start

Ask the system to generate a reviewed plan for a feature and pause at the human gate.

Frequently Asked Questions about lp-plan

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

FAQPage Schema

How do I create a reviewed plan and pause execution before implementation?▼

To create a reviewed plan and pause execution, trigger a planning request using a command like lp:plan. The system generates a canonical plan, produces artifacts, and stops at a human gate to await your review before implementation.

What is a human gate in a planning workflow?▼

A human gate is a checkpoint in the planning workflow that pauses automated execution. After plan creation and artifact generation, the pipeline halts to ensure a human reviews and approves the plan before any implementation begins.

How do I align my plan with an existing specification?▼

To align your plan with an existing specification, trigger the planning workflow. The system uses spec-driven planning, treating the existing spec as the source of truth to ensure the generated canonical plan matches your requirements.

Can I use the lp-pipeline-orchestrator to sync plan state and artifacts?▼

Yes, the planning workflow enforces orchestration policy via the lp-pipeline-orchestrator. It automatically syncs plan state and produces artifacts through the pipeline while gating execution for human review.

When do I need a canonical planning entrypoint for my workflow?▼

You need a canonical planning entrypoint when you want to ensure planning work aligns with business goals before implementation. It coordinates plan creation, review, and state updates, pausing at a human gate to prevent unreviewed execution.

What are the limitations of pausing at a human gate during plan orchestration?▼

Pausing at a human gate halts the pipeline execution entirely. The orchestration workflow cannot proceed to implementation until user approval is granted, meaning automated, unattended execution is intentionally blocked by design.