status

Summarizes modular-dev project state from graph.json and queue metadata.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Arrosam/Modular-Dev --skill status-arrosam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/Arrosam/Modular-Dev/tree/main/skills/status
Command: npx skills add https://github.com/Arrosam/Modular-Dev --skill status-arrosam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives you a fast, reliable snapshot of a modular-dev project so you can understand what is done, what is blocked, and what should happen next without manually inspecting every file.

Core Features & Use Cases

  • Project Health Summary: Reports zones, nodes, contracts, and shared modules in a single status view.
  • Progress Tracking: Shows completed, pending, failed, and in-progress work with clear ASCII indicators.
  • Queue Awareness: Surfaces active modular-dev work queues so teams can see what is currently being developed.
  • Use Case: A team lead asks for a release checkpoint and gets an immediate overview of completed nodes, locked contracts, and the next developable items.

Quick Start

Ask the status skill to show the current modular-dev project state from graph.json and any active queue files.

Frequently Asked Questions about status

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

FAQPage Schema
How do I check modular-dev project progress and queue status at a glance?▼

To check modular-dev project progress, you can generate an operational dashboard summarizing completion states, active queues, and developable nodes from graph.json metadata.

What is the best way to visualize modular-dev zones, nodes, and shared modules?▼

Visualizing modular-dev zones and nodes requires reading graph.json to report tested contracts and shared modules, providing a single project health summary view.

How do I track active work queues across modular-dev contracts?▼

Tracking active work queues involves inspecting queue metadata to surface in-progress modular-dev contracts and identify the next developable items for your team.

Can I see blocked and completed development nodes without manually inspecting files?▼

Yes, you can see blocked and completed nodes without manual file inspection by generating a concise status dashboard that highlights pending, failed, and completed work.

Does generating a project status report require specific queue metadata files?▼

Generating a project status report requires reading graph.json and any active queue files to extract completion states, locked contracts, and active development queues.

What limitations exist when reporting modular-dev completion states from graph data?▼

Reporting completion states is limited by the accuracy of graph.json and queue metadata, meaning untracked or manually modified files outside these structures will not appear in the status view.