Project Delivery Engine for Openclaw

Project Delivery Engine helps AI agents reliably manage long-running projects with persistent state, structured handoffs, and independent review.

haoyun18881-beep
v0.3.5
Jul 29, 2026
0
75
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install project-delivery-engine

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install project-delivery-engine using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Project Delivery Engine?

Project Delivery Engine is an Openclaw Skills workflow for keeping AI-driven projects on track over days, weeks, or months without losing context, progress, or delivery quality.

It separates project state, evidence, collaboration, and governance so the main agent can continue working steadily while spawning parallel agents, using isolated worktrees, and handing important outcomes to independent review before final delivery. The result is a durable project-management layer for Openclaw Skills that prevents drift, preserves continuity, and makes complex multi-step work safer to execute.

Project Delivery Engine Use Cases

  • Managing a current project that must retain progress, next steps, risks, and delivery context across sessions.
  • Starting a new project from an existing codebase, five-piece set, or inherited workstream.
  • Continuing a paused project after switching windows, models, or returning months later.
  • Organizing delivery files, status notes, and handoff materials as project scope grows.
  • Running multi-agent work with spawn agent tasks, worktrees, and parallel execution.
  • Requiring independent review for important outputs instead of self-approval by the same agent.
  • Preparing project closure, transition notes, and clean handoff documentation.

How Project Delivery Engine Works

  1. The agent inspects the user’s latest instruction and the current project files to determine whether the task is tied to existing project state or is a one-off request.
  2. If the task depends on project state, the skill directs the agent to read references/project-state.md to identify the project root, five-piece set, and required indexes.
  3. For file creation or modification, the agent consults references/project-file-templates.md to keep documents consistent with the project’s metadata and structure.
  4. The agent executes straightforward mainline work directly, while collaboration, parallelization, worktrees, and confirmations are handled according to references/collaboration.md.
  5. When real task decomposition is needed, the agent reads references/taskcard-evidencebundle.md and may spawn agents or split work into isolated streams.
  6. If governance-controlled changes are required, the agent must draft a project-gov propose plan first and only then apply it if the toolchain can express the change safely.
  7. At the end of a task, the agent re-checks project state to decide whether the project should be checkpointed, documented, or cleanly handed off.

Project Delivery Engine Setup

  1. Select the Openclaw Skills skill for project delivery and use it only when the task depends on current project state or explicit project management needs.
  2. Read the project references as needed:
    • references/project-state.md
    • references/project-file-templates.md
    • references/collaboration.md
    • references/taskcard-evidencebundle.md
    • references/project-gov-cli.md
    • references/quickstart-faq.md
  3. For governed changes, always follow the propose-then-apply flow.
# Governance workflow example
project-gov propose
project-gov apply
  1. For machine checks, numbering, launch phrases, and governance file writes, use the project governance CLI references.
  2. If you are unsure how to use the skill or encounter a project-gov error, consult the quickstart FAQ before proceeding.

Project Delivery Engine Data Schema & Taxonomy

Project Delivery Engine organizes project knowledge into a small set of durable reference files and state artifacts so Openclaw Skills can preserve continuity.

Artifact / Reference Purpose Notes
references/project-state.md Defines current project state, root, indexes, and continuation cues Primary source for long-running continuity
references/project-file-templates.md Standard templates for creating or repairing project files Use before adding new docs
references/collaboration.md Collaboration, parallel work, worktree, and confirmation routing Guides multi-agent execution
references/taskcard-evidencebundle.md Task breakdown and evidence packaging Used for real decomposition and review
references/project-gov-cli.md Governance CLI usage, machine checks, numbering, launch phrases, and file writes Controls governed changes
references/quickstart-faq.md First-use help and project-gov troubleshooting Fallback for usage questions

Taxonomy and rules:

  • Mainline execution owns final delivery and merge decisions.
  • Collaboration streams, scripts, and evidence bundles cannot replace the mainline’s completion responsibility.
  • AGENTS.md is limited to project identity, proprietary facts, authorization, and boundaries; it should not duplicate general skill rules.
  • Governance changes must be expressed as project-gov proposeapply whenever documentation, checkpoints, or handoff writes affect governed scope.
  • Only the references required for the current task should be loaded, and selected files must be read fully once chosen.

Project Delivery Engine Advanced Features

  • Persistent project state that survives window switches, model changes, and long gaps between sessions.
  • Multi-agent support via spawn agent workflows and isolated worktrees for parallel execution.
  • Independent review for critical outputs, reducing self-approval risk and improving delivery quality.
  • Governance-first change management using a propose-then-apply pattern for controlled writes.
  • Structured handoff support with checkpoints, delivery notes, and project closure materials.
  • Minimal daily overhead with on-demand reference loading, keeping Openclaw Skills lightweight but durable.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*