mission-pi

Delegate cheap-tier mission tasks to the Pi agent with synchronous commands and structured reports.

Updated May 22, 2026
One-click install
npx skills add https://github.com/MathieuDoyon/mission --skill mission-pi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mission-pi
Source: https://github.com/MathieuDoyon/mission/tree/main/.claude/skills/mission-pi
Command: npx skills add https://github.com/MathieuDoyon/mission --skill mission-pi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

mission-pi reduces cost and turnaround time by offloading low-risk, cheap-tier work to the Pi agent while the main orchestrator stays in control of mission progress.

Core Features & Use Cases

  • Pi availability delegation: Checks whether the Pi agent binary is usable before running any delegated task.
  • Deterministic handoff + reporting: Forwards a delegation prompt synchronously to Pi, captures stdout/stderr, and converts results into a structured mission-report for the orchestrator.
  • Blocked escalation: If Pi appears blocked, it clearly signals failure so the orchestrator can reroute the work back to the primary sub-skill.

Quick Start

Ask Claude to route the next cheap-tier task (such as mission-tdd or mission-debug) to Pi by invoking the mission orchestrator with your objective.

Frequently Asked Questions about mission-pi

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

FAQPage Schema
How do I delegate cheap coding tasks to an external agent safely?

Delegating cheap coding tasks safely requires offloading low-risk work to the Pi agent via a synchronous command with a constructed prompt, while the main orchestrator retains mission control and verifies completion using git diffs.

What is agent routing for budget control in orchestrator-driven development?

Agent routing for budget control assigns cost-tiered sub-skills, like TDD or debugging missions, to the first available external agent to reduce turnaround time and manage computational overhead within an orchestration pipeline.

How do I handle agent blockage during automated task delegation?

Handling agent blockage involves capturing stdout and stderr with a timeout, then emitting a structured mission-report that signals failure so the orchestrator can reroute the work back to the primary sub-skill.

Do I need to check Pi availability before running a delegated mission?

Yes, a Pi pre-flight availability checking step is required to verify the agent binary is usable before forwarding any synchronous delegation prompt for low-cost mission work.

Can I use this agent delegation approach for TDD and debugging missions?

Yes, orchestrator-driven scenarios apply to cheap-tier sub-skills like mission-tdd and mission-debug, attempting them on the first available external agent for deterministic handoff and reporting.

What are the limitations of routing cheap-tier work to the Pi agent?

Limitations include strict timeout constraints and dependency on Pi availability; if the agent appears blocked, it cannot complete the task and must escalate failure back to the orchestrator for rerouting.