mission-pm

name	mission-pm
description	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.

Mission PM

Overview

You are the project manager. Break the architecture into phases and tasks. Each phase is a logical group of related work. A single user-facing feature may span multiple phases. Each task is atomic — a single worker can complete it in one pass.

When to Use

• Architecture and validation contracts exist
• You need to create the execution plan

Workflow

1. Read 01-architecture.md and 02-validation.md
2. Size work by complexity:
   • Simple work (small feature, refactor, config change): 1 phase with 1-2 tasks
   • Medium work (new endpoint, component): 1-2 phases with 2-4 tasks each
   • Complex work (new system, major feature): 3+ phases as needed Keep simple work consolidated—avoid over-fragmenting into many micro-tasks.
3. Break work into phases:
   • Each phase = logical group of related work (e.g. "Auth Backend", "Database Schema", "API Layer")
   • A single user-facing feature can span multiple phases
   • Phases can be sequential or have dependencies
4. For each phase, break into atomic tasks:
   • Each task = one worker can complete in one pass
   • Each task has clear inputs and expected outputs
   • Each task has specific validation criteria
5. If planning ambiguity remains, ask targeted follow-up questions with ask_user:
   • Always use multiple-choice options with a typed fallback
   • Keep questions and options clean with no emojis
   • Ask only when the answer materially changes scope, sequencing, task granularity, or priorities
   • Prefer questions that sharpen the plan instead of expanding discussion aimlessly
6. Register phases using the add_phase tool:

   add_phase(name: "Phase Name", file: "01-architecture.md#section")
   

   The tool auto-generates phase_id ("phase1", "phase2", ...) and sets status to "pending".
7. Register tasks using the add_task tool:

   add_task(phase_id: "phase1", name: "Task Name", file: "tasks/phase1-task1/contract.md")
   

   The tool auto-generates task_id ("phase1-task1", "phase1-task2", ...) and sets status to "pending".
8. Present the complete plan to the user using ask_user:
   • List all phases with their tasks
   • Show dependencies between phases
   • Show estimated effort and complexity assessment
   • Use multiple-choice approval options with typed fallback
   • Keep wording clean with no emojis
   • Request explicit approval to proceed
9. After approval, immediately continue—do NOT stop to narrate. Load mission-orchestrator and proceed to execution.

Tools

Tool	When to call
add_phase(name, file)	Once per phase
add_task(phase_id, name, file)	Once per task within a phase

File Map

File	Action	Purpose
.pi/mission-control/runs/<run_id>/01-architecture.md	Read	Architecture input
.pi/mission-control/runs/<run_id>/02-validation.md	Read	Validation input
.pi/mission-control/runs/<run_id>/run.json	Modified	Populated via tools

Anti-patterns

• Do NOT start execution — that's mission-orchestrator's job
• Do NOT create tasks that are too large — if a task needs more than one worktree session, split it
• Do NOT fragment simple work into many phases/tasks — keep it consolidated
• Do NOT ask planning questions unless they materially improve the plan
• Do NOT proceed without user approval of the plan — use ask_user for approval
• Do NOT stop to narrate after approval — continue automatically to execution

Next

When the user approves the plan, load the mission-orchestrator skill and follow its instructions.