soda-loop-status

Parse soda-loop run files into a read-only status dashboard.

Updated Jan 31, 2026

Search Tags:#automation #development workflow #monitoring #status #progress #loop

Ready to run

npx skills add https://github.com/whatasoda/agent-extensions --skill soda-loop-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: soda-loop-status
Source: https://github.com/whatasoda/agent-extensions/tree/main/plugins/dev-workflow/skills/soda-loop-status
Command: npx skills add https://github.com/whatasoda/agent-extensions --skill soda-loop-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a clear, at-a-glance status update for ongoing or completed "soda-loop" runs, eliminating the need to manually parse complex log files and progress reports.

Core Features & Use Cases

Unified Status Dashboard: Consolidates information from PROGRESS.md, session logs, VISION.md, and STOP files into a single, easy-to-understand view.
Progress Tracking: Shows current progress, pending items, blocked tasks, and session costs.
Drill-down Capability: Allows users to investigate specific phases, blocked items, vision goals, or session logs.
Use Case: After initiating a long-running autonomous loop with soda-loop-setup, you can use this skill to quickly check its current progress, identify any bottlenecks, and review the costs incurred so far without sifting through raw output files.

Quick Start

Check the status of the current soda-loop run.

Frequently Asked Questions about soda-loop-status

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

FAQPage Schema

How do I monitor the progress of an autonomous development loop without reading raw logs?▼

You can monitor an autonomous development loop by using a unified status dashboard that parses PROGRESS.md and .loop-logs/ files to display progress, pending items, and session costs.

What is the best way to check session costs and blocked items in a soda-loop run?▼

Checking session costs and blocked items in a soda-loop run is done by drilling down into session logs and progress files, consolidating data from VISION.md and STOP files into a single readable view.

How does parsing VISION.md and STOP files help track development workflow status?▼

Parsing VISION.md and STOP files tracks development workflow status by extracting vision goals and halt conditions, integrating them with session logs to reveal bottlenecks and current progress.

Can I view specific phase details and session history from .loop-logs/ without manual parsing?▼

You can view specific phase details and session history from .loop-logs/ through drill-down capabilities that parse the logs automatically, eliminating the need to manually sift through raw output files.

Does the soda-loop status dashboard modify the PROGRESS.md file during monitoring?▼

The soda-loop status dashboard does not modify PROGRESS.md during monitoring, operating as a read-only interface that parses progress files, session logs, and STOP files to display run status.