Creates data visualizations using only Unicode characters within markdown. No HTML, SVG, or images — pure block, braille, shade, and line-drawing characters that render in any markdown viewer. Use when evidence, data tables, or numerical findings need an honest visual form inside a markdown report.
Systematically diagnose and fix software bugs across five layers—reported symptom, direct cause, neighboring paths, recurring patterns, and systemic safeguards. Use when asked to investigate, debug, bug-hunt, fix all related issues, audit regressions, analyze recurring failures, or prevent a bug family from returning.
Produces user-facing answer reports from prior artifacts in the chain. Does not search or verify; leaves those steps to Searcher and Verifier. Use when a numbered answer report needs to be written from evidence packets, analysis packets, and the goal artifact.
Reads raw files in batch and extracts content-grounded fragments. Writes extraction packets and navigation maps. Use when raw files need batch processing for extraction of content-grounded retrieval fragments.
Session log retrospective and corpus coverage gap detector. Loads the agent-interception skill to read session logs, builds file-access maps, and cross-references against the corpus to identify untouched topics, stale evidence, and underutilized agents. Use when coverage audit is needed to find gaps, stale areas, or underutilized agents.
Audits repo hygiene, evaluates staleness, and proposes archival moves to .trash/. Never deletes files — moves them to .trash/. Always leaves a durable cleanup artifact before any confirmed move. Use when the workspace needs hygiene audit, stale file detection, or archival cleanup.
Provides broader contextual analysis as a sequential artifact-producing step in the chain. Challenges assumptions, identifies gaps, and offers alternative framings. Use when prior artifacts exist and the orchestrator needs broader analytical perspective on the same question.
Audits completed non-fast-path routes, records process-quality findings, and decides whether a tightly scoped framework edit is justified. Use when a non-fast-path route has completed and needs process audit.