init-worktrack-skill

Initialize Harness worktracks with branches, baselines, contracts, and seeded queues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents worktrack scheduling from starting with missing or inconsistent branches, baselines, contracts, or queue seeds by performing a controlled initialization step in Harness WorktrackScope.initializing.

Core Features & Use Cases

  • Worktrack initialization state transition: Creates or repairs the minimal artifacts required for a worktrack to become schedulable, including branch, baseline references, contract, and the initial plan/queue.
  • Milestone-derived safeguards: When the worktrack is derived from an active milestone, it enforces intake review gating by requiring a ready_for_worktrack_init verdict and blocks when refresh/adjust/blocked conditions are present.
  • Dispatch handoff packaging: Produces only the scheduling handoff package needed by downstream dispatch skills, without generating authoritative dispatch packages itself.

Quick Start

Use the init-worktrack-skill when Harness determines a specific worktrack must enter a limited-scope initialization phase and you need it to create the required artifacts and seed the initial scheduling queue.

Frequently Asked Questions about init-worktrack-skill

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

FAQPage Schema
How do I initialize a worktrack for scheduling without missing baseline references or contracts?

Worktrack initialization creates the required scoped branch, baseline references, worktrack contract, and seeded initial plan/queue so it becomes schedulable. It performs a controlled state transition to ensure no missing or inconsistent artifacts block downstream dispatch.

What is worktrack initialization state transition in Harness?

Worktrack initialization state transition creates or repairs the minimal artifacts required for a worktrack to become schedulable, including the scoped branch, baseline references, contract, and the initial plan/queue within the initializing scope.

How do I gate milestone-derived worktracks before scheduling?

Milestone-derived worktracks enforce intake review gating by requiring a ready_for_worktrack_init verdict. The initialization blocks automatically when refresh, adjust, or blocked conditions are present on the active milestone.

Does worktrack initialization generate authoritative dispatch packages?

Worktrack initialization does not generate authoritative dispatch packages. It outputs only a dispatch handoff package containing the scheduling artifacts needed by downstream dispatch skills to safely take over.

When should I use worktrack initialization for git branching and milestone gating?

Use worktrack initialization when Harness determines a specific worktrack must enter a limited-scope initialization phase. It applies to new or recovering worktracks in the initializing scope, including milestone-derived worktracks requiring pre-init intake review gating.

Why does worktrack scheduling fail with missing baseline or contract alignment errors?

Worktrack scheduling fails when baseline determination, contract alignment, or milestone validation constraints are not satisfied. Initialization applies these constraints explicitly and uses stop gating to prevent scheduling until artifacts are created.