pipeline-status-protocol

Read and write pipeline status files using a JSON schema.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/ductrung-nguyen/Orca-vscode --skill pipeline-status-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-status-protocol
Source: https://github.com/ductrung-nguyen/Orca-vscode/tree/main/.github/skills/pipeline-status-protocol
Command: npx skills add https://github.com/ductrung-nguyen/Orca-vscode --skill pipeline-status-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized method for managing and updating the status of a multi-stage pipeline, ensuring consistent tracking of progress, failures, and outputs across all development stages.

Core Features & Use Cases

  • Centralized Status Management: Maintains a single status.json file for all pipeline stages.
  • Stage Tracking: Tracks the status (pending, in-progress, completed, failed, skipped) and output of each defined stage.
  • Error Handling: Records failure reasons and allows for pipeline resumption from specific stages.
  • Task Progress: Supports detailed tracking of individual tasks within the implement stage.
  • Use Case: When developing a new feature, this Skill ensures that each step from discovery to PR creation is logged, its status is updated in real-time, and any issues encountered are clearly documented for easy debugging and continuation.

Quick Start

Update the pipeline status to mark the 'discover' stage as completed with its output file.

Frequently Asked Questions about pipeline-status-protocol

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

FAQPage Schema
How do I track pipeline status across multiple project stages?

To track pipeline status across multiple project stages, you can use a standardized JSON schema to log stage states like pending, completed, or failed in a centralized status file. This protocol ensures consistent progress tracking from discovery through finalization.

How do I manage task progress and error reporting within a pipeline stage?

You can manage task progress and error reporting by updating the pipeline status JSON file. It supports detailed tracking of individual tasks within the implement stage and records failure reasons to allow pipeline resumption from specific points.

What is a pipeline status protocol and when do I need it?

A pipeline status protocol is a standardized method for reading and writing status files across project stages. You need it to ensure consistent tracking of progress, failures, and outputs during multi-stage development workflows.

Can I resume a failed pipeline from a specific stage?

Yes, you can resume a failed pipeline from a specific stage. The protocol handles error reporting by recording failure reasons in the status file, allowing you to identify the failure point and continue the workflow.