kbd-status

Aggregate orchestrator state and progress ledger into a structured KBD status report.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/GQAdonis/turboquant-rs --skill kbd-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kbd-status
Source: https://github.com/GQAdonis/turboquant-rs/tree/main/.opencode/skills/kbd-process-orchestrator/skills/kbd-status
Command: npx skills add https://github.com/GQAdonis/turboquant-rs --skill kbd-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shows the current KBD process state for the active project, consolidating progress across tools to improve visibility and coordination.

Core Features & Use Cases

  • Reads the orchestrator state and progress ledger to produce a complete status summary.
  • Displays project name, active phase, changes, and cross-tool visibility for teams.
  • Useful for status reporting, planning, and coordinating work across tools like Antigravity, Roo, Cursor, Cline, and Codex.

Quick Start

Query the orchestrator state and progress ledger to generate a concise KBD status report for the active project.

Frequently Asked Questions about kbd-status

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

FAQPage Schema
How do I track cross-tool project status and progress in one view?

To track cross-tool project status, aggregate the orchestrator state and progress ledger to display the project name, active phase, and workflow changes. This provides a consolidated status summary for teams coordinating across multiple tools.

What is a KBD process status report and when do I need it?

A KBD process status report surfaces the active project identity, current waypoint, and phase artifacts from the orchestrator. You need it when coordinating workflows across tools like Antigravity, Roo, Cursor, Cline, and Codex to improve visibility.

How do I generate a status report from the orchestrator state and progress ledger?

Generate a status report by querying the orchestrator state and progress ledger to render structured output. This displays the project name, active phase, workflow changes, and next actions required for cross-tool coordination.

Does this project status tracker work with Antigravity, Roo, Cursor, Cline, and Codex?

Yes, this project status tracker works across Antigravity, Roo, Cursor, Cline, and Codex. It reads the orchestrator project identity file and phase progress to provide cross-tool visibility for teams.

What's the best way to consolidate workflow changes and next actions for cross-tool coordination?

The best way to consolidate workflow changes is to read the current waypoint and phase artifacts from the orchestrator. This renders a structured status output showing project name, active phase, and next actions for cross-tool coordination.