tracker-publish

Publish Claude Harness dependency groups to Linear/Jira tracker tasks.

3|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill tracker-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tracker-publish
Source: https://github.com/cwijayasundara/claude_harness_eng_v5/tree/main/.claude/skills/tracker-publish
Command: npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill tracker-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of publishing approved Claude Harness dependency groups to Linear/Jira-compatible tracker tasks, facilitating the handoff between the Claude Harness orchestrator and the external tracker.

Core Features & Use Cases

  • Dependency Group Publication: Publishes approved story groups to an external tracker like Linear or Jira.
  • Tracker Mapping Contract: Writes the local tracker mapping contract that the standalone orchestrator uses.
  • Operating Model: Mirrors approved story groups into an external tracker and prepares the handoff contract for a standalone orchestrator.
  • Granularity Control: Supports different granularities (group, story, single) for mapping issues to tracker tasks.
  • Use Case: Ideal for projects where Linear or Jira serves as the primary work queue and human review surface, allowing for an automated workflow that mirrors Claude Harness's planning and verification processes.

Quick Start

Run the tracker-publish skill with the desired options, such as selecting the provider (linear or jira) and granularity (group, story, or single).

Frequently Asked Questions about tracker-publish

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

FAQPage Schema
How do I automate publishing Claude Harness dependency groups to Linear or Jira?

Publishing dependency groups to Linear or Jira is automated by this Skill, which mirrors approved story groups into tracker issues and writes the local tracker mapping contract for a standalone orchestrator to consume.

What granularity options are supported when mapping Claude Harness stories to tracker issues?

Mapping Claude Harness stories to tracker issues supports group, story, and single granularities, allowing you to control whether dependencies are published as grouped tasks, individual stories, or single issues in Linear or Jira.

How does dependency mapping work when exporting Claude Harness groups to a project tracker?

Dependency mapping exports Claude Harness groups to a project tracker by translating approved story group dependencies into tracker issues and managing the handoff contract required by an external orchestrator for subsequent execution.

Can I use this with Linear and Jira APIs for automated task creation?

Yes, you can use this with Linear and Jira APIs for automated task creation, as it integrates with external tracker APIs to mirror Claude Harness planning and verification processes directly into your primary work queue.

Do I need an external orchestrator to process the tracker mapping contract?

Yes, you need an external orchestrator to process the tracker mapping contract, because the Skill writes the local mapping file specifically for a standalone orchestrator to consume during the downstream execution handoff.