h-status

Reports read-only Haft project status, decision coverage, drift, and spec lifecycle state.

1.4k|102|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/m0n0x41d/haft --skill h-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: h-status
Source: https://github.com/m0n0x41d/haft/tree/main/internal/cli/skill/h-status
Command: npx skills add https://github.com/m0n0x41d/haft --skill h-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams using Haft lose track of which decisions, problems, evidence, and specs are current, stale, or uncovered. This Skill gives the agent a read-only cockpit over the project memory graph so operators can answer status, resumption, and coverage questions without mutating any artifacts.

Core Features & Use Cases

  • Project status cockpit: Queries the Haft MCP server for compact or full status over active problems, decisions, notes, evidence freshness, drift events, and commissions, with scope-aware retries when multiple project scopes exist.
  • Coverage and link-gap inspection: Reports module decision coverage and bounded exact affected_files link gaps from the current derived code index, distinguishing uncovered files from stale or drifted decisions.
  • Typed memory neighborhood reads: Retrieves an exact EntityOfConcern neighborhood via the agent_orientation.v2 projection with explicit read budgets, facet coverage states, and staleness reporting.
  • Human gate briefs: When status exposes a real gate, it inspects the read-only basis and produces a self-contained brief with options, trade-offs, evidence freshness, and a recommendation.
  • Use Case: After a weekend break, ask the agent what needs attention in the project; it returns current decisions, drifted artifacts, uncovered files, and spec lifecycle state without changing anything.

Quick Start

Ask the agent to show the current Haft project status and tell you which decisions, files, or specs need attention.

Frequently Asked Questions about h-status

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

FAQPage Schema
How do I check Haft project status and decision coverage?

Ask the agent for project status; it calls haft_query with action status for a compact cockpit, then coverage for module decision coverage and affected_files link gaps. Use the full flag or related queries for drill-downs on specific files or artifacts.

What is the difference between h-status, h-verify, and h-spec?

h-status is strictly read-only: it reports current graph state, coverage, and spec lifecycle without mutating anything. Use h-verify to gather new evidence and h-spec to edit specifications; h-status never edits, approves, or rebaselines.

Does h-status modify project artifacts or specs?

No. h-status is read-only by design and never calls refresh mutations, closes problems, attaches evidence, edits specs, or creates artifacts. It only reports state and names the read-only calls that can recover hidden detail.

Why does coverage report unavailable or stale results?

Coverage is a projection over stored module data and the current derived code index. If that index is uninitialized, stale, or degraded, h-status reports the limitation as unavailable rather than showing an empty-clean result, and a separately authorized refresh is required.

When should I not use h-status?

Do not call it when there is no status, resumption, coverage, or recorded-state question, and never call it after completed reasoning just to backfill process compliance. It also does not infer project phase or prescribe a universal next step.