quest-create

Generate QUEST.md, PHASES.md, STATE.md, and a .planning/ directory from a user goal.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crafting structured quests and phased execution plans from vague goals is error-prone and time-consuming. This skill automates turning a user goal into a formal QUEST.md, PHASES.md, and STATE.md, ensuring consistency and traceability.

Core Features & Use Cases

  • Automated goal-to-plan translation: converts a goal into a multi-phase plan with clear objectives and status.
  • End-to-end quest lifecycle: creates planning artifacts in a dedicated .planning/ directory and documents necessary metadata.
  • Event emission and state tracking: signals quest creation and maintains a structured state log for auditing.

Quick Start

Invoke /quest-create with your goal description to generate the phased quest plan.

Frequently Asked Questions about quest-create

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

FAQPage Schema
What is the best way to generate structured planning artifacts for a new development workflow?

Generating planning artifacts like QUEST.md, PHASES.md, and STATE.md provides structured documentation for software workflows. It creates a dedicated directory to store these files, handling repository context and metadata.

How does state tracking work for automated quest planning?

State tracking for development workflows is maintained through a structured STATE.md file and event emission. This approach signals quest creation and provides an auditing log for the end-to-end lifecycle.

How does state tracking work for automated quest planning?

State tracking for development workflows is maintained through a structured STATE.md file and event emission. This approach signals quest creation and provides an auditing log for the end-to-end lifecycle.

Can I use this for DevOps automation and documentation generation?

Yes, you can use this for DevOps automation and documentation generation. It is designed for software engineering and product development workflows, converting vague goals into formal, traceable plans.