Paseo Epic is a heavy-ceremony orchestrator skill that runs multi-hour engineering epics end-to-end: preferences → research → capture intent → plan → adversarial review → implement → deliver. It enforces an immutable Requirements block that guides planners and implementers, isolates worktrees when requested, and supports autopilot modes for unattended runs while preserving strict gates and confirmations.
Use this skill when the user requests an 'epic', a long-running feature, or an end-to-end build that must be reproducible and auditable. It's appropriate for multi-phase changes, architecture reshapes, or when work will run overnight and cannot re-litigate scope. Not for ad-hoc small fixes.
Designed to work with agent runners and provider models that support spawning long-lived planners and implementers (examples: Claude Code, Codex, Copilot integrations, Gemini-capable providers).
Paseo Epic is an orchestration skill for long-running resumable engineering epics. However, the SKILL.md body could not be retrieved — the GitHub path (skills/paseo-epic/SKILL.md) returns 404, and the skill appears to have been removed or renamed in the repo. Available skills are paseo-advisor, paseo-committee, paseo-handoff, and paseo-loop. With no body or scripts to review, the skill cannot be used as-is and may be a stale DB entry.
Stale entry — the skill slug 'paseo-epic' does not exist in the getpaseo/paseo repo. The repo has paseo-advisor, paseo-committee, paseo-handoff, paseo-loop, and paseo instead. Consider re-discovering the actual skills or removing this stale entry. Security scored conservatively at 72 (no body to flag issues, but also nothing to verify as safe). Code quality and architecture scored low due to missing content.