Paseo Epic

Heavy-ceremony orchestrator. Runs research → plan → implement → deliver as one resumable flow. The plan file at ~/.paseo/plans/<slug>.md is the source of truth and survives compaction.

This usually runs for hours, often overnight. By the time agents are working, you cannot re-litigate intent with the user. Capture the requirements they have already given you in conversation — behaviors, the "why," UX rules, constraints — and write them into the plan as immutable before any planning agent spins up. Everything downstream (planner, adversarial reviewer, implementers) optimizes around those requirements; it does not relitigate them.

User's request: $ARGUMENTS

Prerequisites

This is a Paseo skill. Load the paseo skill first — it carries the surface (worktrees, agents, waiting, heartbeats, preferences). Every agent you spawn reads it too.

Before choosing any provider, read ~/.paseo/orchestration-preferences.json. Do not create planner, reviewer, researcher, implementer, or auditor agents until you have read it.

Do not use your own subagents. All agents in this skill are Paseo agents, spawned through the Paseo MCP. Your harness's native subagent stack is not in play here.

The role and phase-type vocabulary lives in the roles reference shipped with this skill (references/roles.md).

Modes