Overview

Streaming Progress emits real-time progress events for streaming UI consumption. It formats each event with a timestamp and stage information, computes a completion percentage, and outputs both a human-readable summary and a machine-readable payload for rendering.

How This Skill Works

It receives progress events from the execution stage, enriches them with a timestamp and stage details, and computes a completion percentage. It then generates a human-readable summary and attaches machine-readable data before emitting the formatted event for UI consumption.

When to Use It

• Streaming progress for feature delivery in automaker projects
• Real-time dashboards tracking multi-stage pipelines
• UI components that display live build or test progress
• Orchestrator-driven workflows requiring synchronized progress events
• Debugging and auditing progress through raw event data

Quick Start

1. Step 1: Wire the Progress Streamer into your pipeline (automaker-progress-streamer)
2. Step 2: Emit a progress event with projectName, featureId, and event (stage, message, data)
3. Step 3: Consume the emitted event in the streaming UI and dashboards

Best Practices

• Define a stable stage taxonomy to map progress
• Keep the emitted payload lightweight while including essential data
• Ensure consistent timestamp formatting across environments
• Validate inputs (projectName, featureId, event) before emission
• Provide both human-readable and machine-readable fields for UI rendering

Example Use Cases

• Streaming progress for a new 'Autonomous Drivetrain' feature rollout
• Batch progress for automaker orchestrator during Phase 3 (automaker-orchestrator.js)
• Real-time UI for feature development tracking in a multi-stage pipeline
• Monitoring all stages in the automaker agent-execution.js lifecycle
• Audit trail generation by emitting machine-readable progress metrics

Frequently Asked Questions