deevs-pi-kit

Use for long-running commands that must stay observable, such as dev servers, watchers, REPLs, services, or workers. Prefer managed proc_* tools over shell backgrounding.

Create source-grounded visual explanations such as codebase maps, flows, sequence diagrams, state machines, and architecture views. Prefer compact Mermaid; use SVG/HTML only for polished artifacts.

Run a disciplined debugging loop for broken behavior, failing builds, flaky commands, hung processes, or regressions. Use when the user asks to diagnose, debug, or find root cause.

Build, query, and maintain curated markdown wikis with schema/index/log discipline. Use for project/domain wikis, durable research notes, source ingestion, linting, or canonicalized chain findings.

Use the interactive ask_user UI when 1-5 concrete clarifications or decisions materially affect implementation, scope, safety, or acceptance criteria. Gather evidence first; do not ask what tools can answer.

Create, fork, search, list, and load multi-session chain links under .chains. Use when saving work context, resuming a project from previous sessions, passing context to subagents, or finding prior decisions/next steps.

Use Pi's `todo_list` tool to plan and track non-trivial current-session work. Use for multi-step implementation, debugging, validation, research, or coordinating subagents; avoid for one-shot answers.

Use curated Deevs staff subagents for background exploration, review, testing, architecture, devops, language-specific review, and anti-slop passes.

Use the `pup` CLI to inspect and operate Datadog safely. Use when the user asks about Datadog logs, metrics, monitors, APM/traces, incidents, dashboards, SLOs, Live Debugger, Service Catalog, or Pup itself.

Run a bounded test and review pass for completed or proposed changes. Use when the user asks to test, verify, review before merge, check requirements, run e2e/smoke tests, or make sure a change is not sloppy.

Search, triage, and cite arXiv papers. Use when the user asks for arXiv/preprint/academic paper discovery, recent ML/AI/science papers, paper metadata, abstracts, or BibTeX. Prefer arxiv_* tools over ad-hoc curl.

Map an unfamiliar code area before editing. Use when the user asks to "orient me", "zoom out", "map this area", asks where something fits, or when a safe next action requires understanding multi-file, module, crate, or subsystem relationships.

Run a one-question-at-a-time decision pressure test for plans, designs, APIs, refactors, or product scope. Use when the user says "grill me", wants assumptions challenged, needs tradeoffs resolved, or is about to start implementation from an uncertain plan.