worktrack-status-skill

Generate a WorktrackStateEstimate from worktrack evidence, queue, contract, and branch drift.

29|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/OceanEyeFF/servo --skill worktrack-status-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktrack-status-skill
Source: https://github.com/OceanEyeFF/servo/tree/main/product/harness/skills/worktrack-status-skill
Command: npx skills add https://github.com/OceanEyeFF/servo --skill worktrack-status-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves uncertainty about what a worktrack is currently “in” by producing a structured, repeatable state estimate from the official worktrack evidence, queue, contract, and branch divergence signals.

Core Features & Use Cases

  • WorktrackScope observing state transitions: Converts observing-scope inputs into a consistent WorktrackStateEstimate for the Harness control loop.
  • Evidence-driven status estimation: Detects evidence deltas, blocker status, acceptance coverage gaps, and branch drift to explain why the worktrack is (or isn’t) ready for the next decision stage.
  • Next-operator handoff (non-decisional): Provides recommended routing hints (e.g., Decide/Recover/Close/Verify) while explicitly staying within “observe” rather than planning or dispatching.

Quick Start

Ask the Harness to run worktrack-status-skill when the current problem is “what state is the worktrack in?” so it can return a narrow-scope worktrack state estimate ready for the subsequent decide/recover/verify steps.

Frequently Asked Questions about worktrack-status-skill

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

FAQPage Schema
How do I estimate the current state of a worktrack before making schedule or dispatch decisions?

To estimate worktrack state, observe the current worktrack scope using the Worktrack Contract, Plan/Task Queue, evidence outputs, and branch drift to generate a structured WorktrackStateEstimate. This provides state clarity before schedule, dispatch, or review decisions are made.

What is branch drift detection and when do I need it for agent orchestration?

Branch drift detection compares branch divergence against baseline signals to assess readiness. It is needed during agent orchestration when evaluating evidence outputs and acceptance coverage to determine if a worktrack is ready for the next decision stage.

How do I assess queue and evidence alignment for a harness control loop?

Assess queue and evidence alignment by checking freshness, acceptance coverage, and blocker status against the Worktrack Contract. The harness control loop uses this alignment evaluation to determine if inputs are valid or stale before proceeding.

When should I stop worktrack observation due to missing or contradictory inputs?

Stop worktrack observation when inputs are missing, stale, or contradictory. Stop conditions must be enforced during state estimation to prevent invalid WorktrackStateEstimate generation when queue, contract, or evidence data fails readiness checks.

Can I get worktrack routing hints without triggering planning or dispatch actions?

Yes, you can get recommended routing hints such as Decide, Recover, Close, or Verify while explicitly staying within the observe scope. The state estimate provides next-operator handoff recommendations without executing planning or dispatching actions.

Does worktrack status estimation work for recovery and closure contexts?

Worktrack status estimation applies to recovery and closure contexts by evaluating evidence deltas and blocker status. It generates the WorktrackStateEstimate needed to clarify state before deciding whether to recover, verify, or close the worktrack.