harness-status

Analyze local Harness state to determine the current development phase.

8|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/zxdxjtu/harness --skill harness-status-zxdxjtu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-status
Source: https://github.com/zxdxjtu/harness/tree/main/skills/harness-status
Command: npx skills add https://github.com/zxdxjtu/harness --skill harness-status-zxdxjtu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recover context and determine the current development phase to streamline sprint planning and issue resolution.

Core Features & Use Cases

  • Read local harness state from .harness, specs, tasks, progress, sprint-loop, pitfalls, invariants, traces, and recent git history.
  • Produce a phased health snapshot and suggested next steps for project leadership and engineers.
  • Provide an actionable health check and evolution suggestions to improve automation.

Quick Start

Run the /harness-status command to retrieve the current project status and suggested 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 my Harness project status and current development phase?

Run the /harness-status command to analyze local state from the .harness directory, including specs, tasks, progress, and git history. It produces a phase and health snapshot that recovers context and determines the current development phase for sprint planning.

What is Harness state recovery and when do I need it for sprint planning?

Harness state recovery reads local project files like sprint-loop, pitfalls, invariants, and traces to rebuild lost context. You need it during sprint planning to assess project health, identify risks, and determine actionable next steps.

Can I use harness-status to read local project state without external dependencies?

Yes, you can use harness-status without external dependencies. It operates locally by parsing the .harness directory and recent git history to generate a health snapshot. This makes it suitable for local development phase detection and risk assessment.

What is the best way to track project health and evolution suggestions in Harness?

The best way to track project health is by reading local harness state from specs, tasks, and traces. This skill provides an actionable health check and evolution suggestions to improve automation, helping project leadership make informed decisions.

Does harness-status work with my existing git history and local specs?

Yes, harness-status works with your existing git history and local specs. It reads the .harness directory, specs, tasks, progress, and recent git history to produce a phased health snapshot and suggested next steps for issue resolution.