pi-mission-control

Distill learnings from a completed mission into persistent long-term memory. Use when a mission finishes or when significant knowledge should be preserved between tasks and phases.

Primary orchestration skill representing the main user-facing pi agent behavior. Acts as Tech Lead, Project Manager, and Interviewer. Handles the complete mission lifecycle: interviews user, produces requirements, guides architecture design, breaks work into phases/tasks, and executes via Worker → Auditor subagents. Worker and Auditor are the ONLY subagents spawned.

Break architecture into phases and atomic tasks, register them using mission-control tools. Use after mission-tech-lead produces architecture and validation. A single feature may span multiple phases.

Research and interview the user to produce a detailed requirements document for a new mission. Use when starting a new mission or when the user wants to define what to build.

Translate requirements into system architecture and validation contracts. Use after mission-research completes and requirements are approved.