quest-run

Automate plan-exec-verify loops for multi-phase quest projects.

2|5|Updated Jan 2, 2026

Search Tags:#automation #orchestration #subagent #phases #quest #plan-exec-verify

Ready to run

npx skills add https://github.com/whoabuddy/claude-knowledge --skill quest-run

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quest-run
Source: https://github.com/whoabuddy/claude-knowledge/tree/main/claude-config/skills/quest-run
Command: npx skills add https://github.com/whoabuddy/claude-knowledge --skill quest-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end execution of multi-phase quests by coordinating plan, execution, and verification steps in isolated subagents to prevent context bleed between phases.

Core Features & Use Cases

Phase-isolated planning, execution, and verification for quest tasks
Per-phase state management using .planning directory and phase metadata
Seamless orchestration with a lean orchestrator that minimizes token consumption

Quick Start

Run /quest-run to start from the current phase, or /quest-run <N> to start at phase N, or /quest-run <N-M> to run a range of phases.

Frequently Asked Questions about quest-run

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

FAQPage Schema

How do I automate multi-phase quest execution without context bleed?▼

Automate multi-phase quest execution by using a lean orchestrator that spins up a fresh subagent per phase, preventing context bleed. This isolates planning, execution, and verification steps while managing state in a .planning directory.

What is the plan-exec-verify loop for quest phases?▼

The plan-exec-verify loop is an orchestration pattern that isolates planning, execution, and verification steps into separate subagents for each quest phase. It ensures tasks are validated before proceeding and manages state via a .planning directory.

How do I start a specific phase or range of phases in a quest project?▼

Start specific phases by running /quest-run <N> to begin at phase N, or /quest-run <N-M> to execute a range of phases. Running /quest-run without arguments starts execution from the current phase automatically.

Can I use subagent orchestration for quest projects with multiple phases?▼

Yes, subagent orchestration supports quest projects with multiple phases by using a lean orchestrator to coordinate phase-specific subagents. It enforces per-phase state management and isolation to prevent context bleed between tasks.

Why does quest automation require a fresh subagent per phase?▼

Quest automation requires a fresh subagent per phase to prevent context bleed. This isolation ensures that accumulated state and context from one phase do not interfere with the planning, execution, or verification of subsequent phases.