skills.rest
daudaudinang
daudaudinangCOMMUNITY
Explore all skills by this author →
GitHub

create-plan

Generate a LittlePea plan package with plan.md, phase manifests, and graphs.

Updated Apr 14, 2026
Search Tags:#automation#planning#orchestration#artifacts#plan#lp
One-click install
npx skills add https://github.com/daudaudinang/vibecode --skill create-plan-daudaudinang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/create-plan
Command: npx skills add https://github.com/daudaudinang/vibecode --skill create-plan-daudaudinang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Worker-only planning support to generate a canonical LittlePea plan package and its machine-readable artifacts, enabling reliable orchestration gates.

Core Features & Use Cases

  • Worker-only: focuses on the create-plan phase without taking over orchestration.
  • Generates plan.md, phase manifests, an ownership graph, and a dependency graph to support review-plan and gating.
  • Use case: when a new planning task arrives, this skill creates a complete plan package ready for orchestration review.

Quick Start

Instruct the worker to create the canonical LP plan package from the current context and output plan artifacts.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I automate the creation of a canonical planning package and its machine-readable artifacts?▼

To automate canonical plan creation, you can use a worker-only skill that generates a complete plan package, including plan.md and dependency graphs, ready for orchestrator review and gating across pipelines.

What planning artifacts are needed for reliable orchestration gates in automation pipelines?▼

Reliable orchestration gates require machine-readable planning artifacts such as plan.md, phase manifests, an ownership graph, and a dependency graph to evaluate and approve workflow progression.

How do I generate phase manifests and dependency graphs for a new planning task?▼

You generate phase manifests and dependency graphs by instructing a worker to process the current context and output the canonical plan artifacts under the designated .codex/plans/ and pipeline paths.

Does this canonical plan creation approach take over the orchestration workflow?▼

No, this canonical plan creation approach operates as a worker-only function, focusing strictly on generating the plan package and its metadata without taking over the primary orchestration duties.

What is the best way to structure a plan package for orchestrator review?▼

The best way to structure a plan package for orchestrator review is to generate a canonical format containing plan.md, phase manifests, and ownership graphs, publishing outputs under .codex/plans/PLAN_<NAME>.

Related Skills

Explore More Software Engineering Skills→
daudaudinangdaudaudinang

create-spec

Generate a testable LP spec package with business context and acceptance criteria.

Community
Intermediate
matochumatochu
4

replan

Integrate review findings or manual edits into versioned plan artifacts.

Community
Advanced
JamkrisJamkris
86

blueprint

Convert a one-line objective into a multi-step construction plan with dependency graphs.

Community
Advanced
daudaudinangdaudaudinang

lp-plan

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

Community
Intermediate