quest-plan

Generate structured phase plans from QUEST.md and PHASES.md into PLAN.md.

2|5|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/whoabuddy/claude-knowledge --skill quest-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quest-plan
Source: https://github.com/whoabuddy/claude-knowledge/tree/main/claude-config/skills/quest-plan
Command: npx skills add https://github.com/whoabuddy/claude-knowledge --skill quest-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates planning of quest phases by generating structured phase plans, reducing manual coordination and enabling faster, consistent execution.

Core Features & Use Cases

  • Read QUEST.md and PHASES.md to determine overall quest goals and phase objectives.
  • Spawn a quest-planner agent in planning mode to craft detailed phase plans.
  • Write PLAN.md under phases/NN-name/ with a structured XML task format and update phase STATE accordingly.

Quick Start

Run /quest-plan to plan the next quest phase.

Frequently Asked Questions about quest-plan

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

FAQPage Schema
How do I automate planning for structured project phases?

Automating phase planning requires reading project goals and phase objectives from markdown files, then generating a structured XML task plan. This approach reduces manual coordination by automatically writing the plan to the correct phase directory.

What is a structured phase plan and when do I need it?

A structured phase plan is a detailed XML task format written to a PLAN.md file, organizing project execution into actionable steps. You need it when managing complex multi-phase projects and requiring consistent, automated coordination across phases.

Do I need a local validation script to generate an XML phase plan?

Yes, generating an XML phase plan requires a local phase validation script and a quest-planner agent in planning mode. These dependencies ensure the generated plan aligns with project context and passes validation checks.

How does an automated agent use existing context to plan the next phase?

The automated agent reads overall goals from QUEST.md and phase objectives from PHASES.md, while considering patterns from previous phases. It then writes the new plan to the specific phase directory and updates the project state.

What are the limitations of using an automated quest planner for task generation?

Limitations include strict dependencies on specific directory structures like .planning/ and required files such as QUEST.md and PHASES.md. Without these exact local files and the validation script, the automated task generation cannot execute.