Skill

mission

Use when the user says "/harness:mission", "create a mission", "start a mission", "check mission status", "approve this task", "reject this task", or wants to create, monitor, or manage autonomous multi-task missions from Claude Code.

Install

npx claudepluginhub lukaleskovsek/makers-and-breakers-claude-marketplace --plugin harness

Tool Access

This skill uses the workspace's default tool permissions.

Preview

<span data-proof="authored" data-by="ai:claude">Create, monitor, and manage autonomous missions from Claude Code. Missions are multi-task workflows executed by The Harness orchestrator — each task spawns an independent Claude CLI session.</span>

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.1k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

claude-code-plugin-release

1 file

Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.

claude-mem

64.7k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 7, 2026

Actions

View Source View Plugin View on GitHub View README

Harness Mission — Autonomous Workflow Control

Create, monitor, and manage autonomous missions from Claude Code. Missions are multi-task workflows executed by The Harness orchestrator — each task spawns an independent Claude CLI session.

Prerequisites

Call harness_status to verify the daemon is running.

Commands

Create a Mission

Ask the user for: title, description, and which repos to target
Call harness_create_mission with the details
Report the mission ID and link to dashboard

Note: Missions need tasks before they can start. Tasks are typically added via the dashboard's decomposition feature or REST API.

Monitor a Mission

Call harness_get_mission to get the overview
Call harness_get_mission_tasks to see all tasks with statuses
Present a text-based progress view:

Mission: {title} [{status}]
Tasks: {completed}/{total} ({running} running, {review} in review)

  [completed] Task 1: Set up database schema
  [running]   Task 2: Implement API endpoints
  [review]    Task 3: Write integration tests  ← needs approval
  [pending]   Task 4: Deploy to staging

Handle Review Gates

When tasks reach review status, they need human approval:

Call harness_get_mission_tasks to find tasks in review state
For each review task, present the task details and ask the user
Based on user decision:
- Approve: Call harness_approve_task — task moves to completed, downstream tasks unblock
- Reject: Call harness_reject_task with feedback — task resets to pending with incremented retry count, feedback appended to description

Start / Pause

Start: Call harness_start_mission — sets status to running, orchestrator begins dispatching tasks
Pause: Call harness_pause_mission — stops new task dispatch, running tasks continue to completion

List Missions

Call harness_list_missions with optional status filter to see recent missions.

Interaction Style

Keep status updates concise — use the text progress view, not verbose descriptions
For review gates, show the task title and any output/artifacts before asking for approval
Don't ask for confirmation on read-only operations (list, get, status)
Do ask for confirmation before start, pause, approve, reject