deep-status

Aggregate deep loop session state from .deep-* files into status reports.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/marcusgoll/deep-loop-plugin --skill deep-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-status
Source: https://github.com/marcusgoll/deep-loop-plugin/tree/main/skills/deep-status
Command: npx skills add https://github.com/marcusgoll/deep-loop-plugin --skill deep-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking the state of autonomous deep loop development sessions requires digging through scattered .deep-* directories and multiple files to find phase, progress, and issues. This Skill automates that lookup to give you a clear, at-a-glance status report in seconds.

Core Features & Use Cases

  • Automated Session Discovery: Scans for active and legacy deep loop sessions automatically, no manual file path hunting required.
  • Comprehensive State Aggregation: Pulls real data from state.json, task files, and session artifacts including issues, error logs, and test results.
  • Use Case: If you are running a multi-agent deep loop build and want to quickly check how many tasks remain, what validation issues were found, or if your session has gone stale, this Skill delivers that information instantly without opening individual files.

Quick Start

Use the deep-status skill to check the current progress and state of your active deep loop session.

Frequently Asked Questions about deep-status

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

FAQPage Schema
How do I check the progress of my autonomous deep loop development session?

To check autonomous deep loop development session progress, you can use a status aggregation tool that scans .deep-* directories and compiles phase, iteration, and task data from state.json files into a single readable report.

Can I see test results and error logs from a deep loop session without opening individual files?

You can retrieve test results and error logs from a deep loop session by aggregating session artifacts automatically, pulling real data from scattered task files and state.json to display issues and validation errors in one consolidated view.

What is the best way to monitor staleness in a multi-agent deep loop build?

Monitoring staleness in a multi-agent deep loop build involves scanning active session state files to generate a human-readable status report that includes staleness warnings and actionable next steps for completed or stalled iterations.

Does deep-status work with internal, external, and quick mode deep loop sessions?

Deep loop session status tracking applies to users running internal, external, or quick mode sessions, automatically discovering active and legacy sessions to provide real-time visibility into task status and phase progression.

How do I find out how many tasks remain in my TDD autonomous development loop?

Finding remaining tasks in a TDD autonomous development loop requires scanning the session's state.json and task files to aggregate iteration progress, extracting actionable next steps and current phase status automatically.