skills.rest
deepklarity
deepklarityOFFICIAL
Explore all skills by this author →
Website𝕏@DeepKlarityGitHub

dk-local-run-spec

Plan, review, and execute Odin specs locally with environment setup and diagnostics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps plan and run Odin specs locally, handling working directories, authentication, nested-session detection, and post-run diagnostics so you can test and smoke-spec workflows safely.

Core Features & Use Cases

  • Plan: Prepare and stage Odin specs for execution with proper environment handling.
  • Safe execution: Detect nested Claude Code sessions and prevent unsafe subprocess runs.
  • Post-run diagnostics: Provide checks to verify results and trace provenance.

Quick Start

Run a local Odin spec with the provided spec path and observe the planned and executed steps.

Frequently Asked Questions about dk-local-run-spec

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

FAQPage Schema
How do I run Odin specs locally in an isolated workflow?▼

To run Odin specs locally, you provide a valid spec path to the Odin CLI within a properly configured repository. The tool plans the execution, handles environment setup, and performs post-run diagnostics safely.

What is needed to execute Odin specs in a local environment?▼

Executing Odin specs locally requires access to the Odin CLI, a valid spec path, and a properly configured repository. These prerequisites ensure the planned execution and diagnostics operate correctly within the isolated workflow.

How does nested-session detection work when testing Odin specs?▼

Nested-session detection works by identifying unsafe subprocess runs during local spec execution. This mechanism prevents conflicts and ensures safe, isolated testing when you plan and run Odin specs.

Can I smoke-test Odin specs without affecting my working directory?▼

Yes, you can smoke-test Odin specs safely. The tool handles working directories, authentication, and environment setup to ensure execution occurs in an isolated, safe workflow without unintended side effects.

Why do my local Odin spec executions fail during environment setup?▼

Local Odin spec executions may fail if the repository is not properly configured or the spec path is invalid. The tool requires these elements to correctly plan, stage, and execute the spec locally.

What is the best way to verify results after running a local Odin spec?▼

The best way to verify results after running an Odin spec is to use the built-in post-run diagnostics. These checks trace provenance and validate the execution outcome of your local spec run.

Related Skills

Explore More Software Engineering Skills→
KamiJeongKamiJeong

speckit-git-commit

Stage and commit repository changes after Spec Kit hook events.

Community
Intermediate
richfremrichfrem
5

spec-kitty-status

Track and verify Spec-Kitty workflow states with provenance-aware checks.

Community
Intermediate
josorio7122josorio7122
1

worktree

Create isolated Git worktrees with dependency installation and baseline tests.

Community
Advanced
BarryYinBarryYin

kiro-validate-impl

Validate feature-level integration and cross-task consistency across implemented tasks.

Community
Advanced