deliver

Orchestrate feature delivery across multiple repositories in a defined workspace.

16|2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/pipecrew-ai/pipecrew --skill deliver-pipecrew-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliver
Source: https://github.com/pipecrew-ai/pipecrew/tree/main/skills/deliver
Command: npx skills add https://github.com/pipecrew-ai/pipecrew --skill deliver-pipecrew-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the delivery of new features across multiple repositories in a workspace, eliminating the need for manual coordination and ensuring consistency across all parts of the system.

Core Features & Use Cases

  • Multi-Repo Orchestration: Automates the process of delivering features across all repositories involved in a project, from requirements gathering to final deployment.
  • Parallel Implementation: Concurrently executes backend, frontend, mock, and infrastructure work to speed up feature delivery.
  • Code Review and Assessment: Incorporates code review and cross-repo assessment to maintain code quality and ensure features meet requirements.

Quick Start

To deliver a feature, run: /deliver "New feature description" --workspace=<workspace-slug>

Frequently Asked Questions about deliver

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

FAQPage Schema
How do I orchestrate feature delivery across multiple repositories?

Multi-repo feature delivery is orchestrated by utilizing a valid workspace configuration file to coordinate requirements, spec editing, implementation, and assessment across all defined repositories. Specialized agents handle each repository type to ensure system-wide consistency.

Can I execute backend and frontend implementation in parallel?

Yes, parallel implementation concurrently executes backend, frontend, mock, and infrastructure work to speed up feature delivery. This concurrent execution is managed by specialized agents assigned to each specific repository type within the workspace.

Do I need a workspace configuration file to deliver a feature?

Yes, a valid workspace configuration file is required to deliver a feature across all workspace repos. You must provide the workspace slug when running the delivery command to ensure proper multi-repo orchestration and feature consistency.

What is the best way to maintain code quality during multi-repo feature delivery?

The best way to maintain code quality is through integrated code review and cross-repo assessment during the feature delivery process. This ensures that the parallel implementation across backend, frontend, and infrastructure meets all requirements and maintains consistency.

Does multi-repo feature orchestration work without Node?

No, multi-repo feature orchestration requires Node as a dependency to run the scripts and specialized agents. The orchestration process for parallel implementation and code review relies on the Node environment to function correctly across all workspace repositories.