command-center

Render status.json, chat.jsonl, and inbox.json into a self-contained HTML dashboard.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill command-center-brucebanner010198-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-center
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/command-center
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill command-center-brucebanner010198-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Consolidates live project status and organizational structure into a single, shareable view, reducing context-switching and misaligned decisions.

Core Features & Use Cases

  • Build a persistent, self-contained HTML dashboard that renders status.json, chat.jsonl, and inbox.json into a single artifact.
  • Visualize the org chart with CEO and 9 councils, plus a 7-phase pipeline and meeting logs for quick decision making.
  • Access artifacts and references locally to verify project state and governance artifacts during board meetings.

Quick Start

Load the live dashboard for the current project with the command-center skill to refresh status, blockers, and artifacts.

Frequently Asked Questions about command-center

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

FAQPage Schema
How do I consolidate live project status and an org chart into a single dashboard for board meetings?

To consolidate live project status and an org chart into a single dashboard, this skill reads status.json, chat.jsonl, and inbox.json to render a self-contained HTML artifact. It visualizes a 9-council org chart, a 7-phase pipeline, and meeting logs for decision making.

What is the best way to render status.json and chat logs into a shareable HTML dashboard?

The best way to render status.json and chat logs into a shareable HTML dashboard is to use a workflow-automation skill that parses these files locally. It generates a self-contained status artifact with embedded state, reducing context-switching during governance reviews.

Can I visualize project blockers and phase progress across councils without manual coding?

Yes, you can visualize project blockers and phase progress without manual coding. The skill automatically applies during board meetings to consolidate live project state from your local JSON files into a pre-structured HTML dashboard with a 7-phase pipeline view.

Does this live dashboard workflow require any external dependencies to render inbox.json and references?

No external dependencies are required to render inbox.json and references. The skill operates independently to access local artifacts and references, verifying project state and governance artifacts directly from the embedded state within the generated HTML.

When do I need a live status artifact for board visibility instead of a static report?

You need a live status artifact for board visibility when you must monitor real-time phase progress, blockers, and artifacts across councils during CEO and board meetings. It reads current JSON files to ensure decisions are based on the latest project state.

Why does my project management dashboard show misaligned decisions during board meetings?

Your project management dashboard shows misaligned decisions because it lacks consolidated live status. By reading status.json and inbox.json to render a single shareable view with an org chart and pipeline, the skill ensures all stakeholders see the same embedded state.