dk-local-inspect

Run local diagnostic scripts to inspect tasks, specs, boards, and reflections.

87|12|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/deepklarity/harness-kit --skill dk-local-inspect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dk-local-inspect
Source: https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/dk-local-inspect
Command: npx skills add https://github.com/deepklarity/harness-kit --skill dk-local-inspect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and inspect the current state of tasks, specs, boards, and reflections by running local diagnostic scripts to reduce guesswork during debugging.

Core Features & Use Cases

  • Directs diagnostic script execution from a consistent repo root and captures outputs in a predictable format.
  • Supports multiple targets (task, spec, board, reflection, snapshot) and verbosity modes (--brief, --full, --json) for flexible debugging.
  • Ideal for investigating failures, validating board state, or auditing reflections before decisions.

Quick Start

Run the quick-start instruction to execute the skill locally and see diagnostic results.

Frequently Asked Questions about dk-local-inspect

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

FAQPage Schema
How do I run local diagnostics to inspect tasks and boards?

Run local diagnostic scripts from the repository root's taskit/taskit-backend directory using testing_tools. This executes local diagnostics to inspect tasks, boards, specs, or reflections and captures their current state in a structured format for debugging.

What targets can I diagnose when auditing reflections or board state?

Supported diagnostic targets include task, spec, board, reflection, and snapshot. Diagnosing these targets allows you to investigate failures, validate board state, or audit reflections before making project decisions.

Can I get diagnostic results in a structured format for LLMs?

Yes, you can use the json output mode to get structured diagnostic results for LLMs. The local diagnostics also support brief and full output modes to fit different debugging scenarios and verbosity needs.

Does inspecting specs require any specific dependencies or environment setup?

Inspecting specs requires no external dependencies, but you must execute scripts from a consistent repo root within the taskit/taskit-backend directory. This ensures the diagnostic scripts capture outputs predictably.

What is the best way to reduce guesswork when debugging task state?

The best way to reduce guesswork is to run local diagnostic scripts to inspect task state directly. This provides predictable, structured outputs that help investigate failures and validate state before making decisions.