do

Routes planning, debugging, and execution requests to deterministic workflows with continuity gates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cometjc/dev-skills --skill do-cometjc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do
Source: https://github.com/cometjc/dev-skills/tree/main/skills/do
Command: npx skills add https://github.com/cometjc/dev-skills --skill do-cometjc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It reduces decision chaos by routing every planning, debugging, and execution request through a single deterministic orchestration path with continuity gates, so you don’t get stuck choosing the wrong workflow or re-litigating stale state.

Core Features & Use Cases

  • Deterministic governance routing: First-hit routing selects exactly one workflow for requests like /do, fix-errors, empty status, diagnostics, and spec clarification.
  • Continuity and review gates: Prevents proceeding when pending AUQ or unconsumed reviewer findings would invalidate the current slice.
  • Empty Status Mode orchestration: Surfaces a durable todo working set, spawns a background status audit, and avoids asking what /do means.
  • Plan execution delegation: Delegates PLD mechanics to the PLD skill while /do focuses on selecting the correct route and recording normalized evidence.

Quick Start

Use /do fix-errors with an existing todo queue when you need the system to route you to the correct execution workflow under governance.

Frequently Asked Questions about do

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

FAQPage Schema
How does deterministic workflow routing handle planning and debugging requests?

Deterministic workflow routing handles planning and debugging by using first-hit routing to select exactly one workflow per request, preventing decision chaos and avoiding the selection of incorrect execution paths.

How do I route fix-errors requests through execution governance?

To route fix-errors requests through execution governance, use the /do fix-errors entrypoint with an existing todo queue, allowing the system to deterministically select the correct workflow and record normalized evidence.

What happens when workflow routing encounters pending AUQ or unconsumed reviewer findings?

When workflow routing encounters pending AUQ or unconsumed reviewer findings, continuity and review gates prevent proceeding to avoid invalidating the current execution slice with stale state.

How does Empty Status Mode orchestrate todo reporting for execution workflows?

Empty Status Mode orchestrates todo reporting by surfacing a durable todo working set and spawning a background status audit, avoiding unnecessary prompts about the /do entrypoint meaning.

Can I use plan execution delegation for PLD mechanics alongside deterministic routing?

Yes, you can use plan execution delegation for PLD mechanics alongside deterministic routing, as the orchestration delegates PLD mechanics to the PLD skill while focusing on selecting the correct route and recording evidence.

Why does workflow routing enforce plan vs execution selection rules?

Workflow routing enforces plan vs execution selection rules to reduce decision chaos and prevent re-litigating stale state, ensuring every request follows a single deterministic orchestration path with continuity gates.