dap-cli

Use when: an agent needs to debug, inspect, or control a local program from shell commands with dap-cli; trigger for DAP debugging, breakpoints, stack/variables inspection, launch.json debugging, js-debug, debugpy, CodeLLDB, Rust, Chrome debugging, Playwright interop, or poll-then-inspect debug loops. Assumes dap-cli is already on PATH.

Use when: cutting a new dap-cli release to npm. Walks through bumping the version, pushing the tag, and creating the GitHub Release that triggers the publish workflow.

Show available GSD commands and usage guide

Ingest external plans with conflict detection against project decisions before writing anything.

Interactive command center for managing multiple phases from one terminal

Create context handoff when pausing work mid-phase

Create detailed phase plan (PLAN.md) with verification loop

Generate developer behavioral profile and create Claude-discoverable artifacts

Check progress, advance workflow, or dispatch freeform intent — the unified GSD situational command

Use when: fully onboarding an approved built-in language/runtime/debug adapter into dap-cli. Runs research, GSD phase planning, implementation, external repo validation, fresh-agent hardening, JSONL transcript audit, and final verification.

Use when: choosing the next language/runtime/debug adapter for dap-cli. Produces an adapter-selection packet and stops for explicit language + adapter signoff before candidate repo research, implementation planning, or GSD execution.