skills.rest
lenlla
lenllaCOMMUNITY
Explore all skills by this author →
GitHub

harness-status

Read .execution-state.yaml files to summarize builds, epics, and steps.

Updated Aug 23, 2026
Search Tags:#automation#workflow#execution#status#claude-code#harness#kyros-agent-workflow
One-click install
npx skills add https://github.com/lenlla/one_shot_build --skill harness-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-status
Source: https://github.com/lenlla/one_shot_build/tree/main/skills/harness-status
Command: npx skills add https://github.com/lenlla/one_shot_build --skill harness-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Presents the current agent harness execution state so users can quickly discover active builds, understand epic and step progress, and decide the appropriate next action without manually searching project files.

Core Features & Use Cases

  • Harness discovery: Verifies presence of a kyros-agent-workflow directory and instructs the user to initialize if missing.
  • Execution state scanning: Locates .execution-state.yaml files via the plugin's state.sh helper and summarizes each build, showing epic-level status and step-level progress when available.
  • Actionable guidance: Displays clear next actions for no-execution, active-execution, and all-complete scenarios and surfaces circuit-breaker warnings with contextual failure information.
  • Use case: Resume a paused model-build run by identifying the current build directory, reviewing the active epic and step, and running the recommended /execute-plan command to continue.

Quick Start

Ask the harness-status skill to show the current workflow status and list any active executions with recommended next steps.

Frequently Asked Questions about harness-status

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

FAQPage Schema
How do I check the status of an active agent workflow execution?▼

You can view active workflow executions by scanning `.execution-state.yaml` files to summarize build progress, epic statuses, and step-level completion. This Skill surfaces current execution states and circuit-breaker warnings directly.

What is the best way to resume a paused model-build run in claude-code?▼

Resuming a paused model-build run involves identifying the current build directory, reviewing the active epic and step from the execution state, and running the recommended `/execute-plan` command. This Skill surfaces the exact next CLI action to continue.

Does the harness-status workflow require a specific project directory structure?▼

Yes, the harness-status workflow requires a `kyros-agent-workflow` directory in your project. If missing, it instructs you to initialize it, and it relies on plugin helpers like `lib/state.sh` to locate execution state files.

How do I find out the next CLI action for an incomplete automation workflow?▼

To find the next CLI action for an incomplete automation workflow, this Skill analyzes the execution state YAML and suggests commands like `/execute-plan`, `/profile-data`, or `/define-epics` based on whether scenarios are active, complete, or halted by circuit-breakers.

Why does my kyros-agent-workflow show a circuit-breaker warning?▼

A circuit-breaker warning appears when the execution state YAML indicates a failure condition. This Skill surfaces contextual failure information from the state files, allowing you to diagnose the exact step and epic where the automation halted.

Related Skills

Explore More Software Engineering Skills→
royhenengelroyhenengel

status

Scan directory structures and Markdown files to generate project status reports.

Community
Intermediate
dot-dodot-do
2

workflow-status

Aggregate discovery.db briefs and beads epics into a single workflow view.

Official
Intermediate
pingmepipingmepi

pm-status

Aggregate PM-OS project stage statuses and activity logs from YAML and Markdown files.

Community
Basic
FaysilAlshareefFaysilAlshareef
4

circuit-breaker

Apply configurable circuit-breaker patterns to .NET HTTP client calls.

Community
Advanced