quest-status

Monitor quest progress, phase status, and retry information from planning files.

2|5|Updated Jan 2, 2026

Search Tags:#automation #planning #status #quest #progress #state #phase

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reliable way to monitor quest progress, phase status, and retry information across planning and execution stages.

Core Features & Use Cases

Monitor quest progress across phases
Display current phase status and retry information
Read details from .planning/QUEST.md, PHASES.md, and STATE.md for context

Quick Start

Run /quest-status to view the current quest progress and phase status.

Frequently Asked Questions about quest-status

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

FAQPage Schema

How do I track quest progress and phase status during an ongoing workflow?▼

To track quest progress, run a status command that parses planning files like QUEST.md, PHASES.md, and STATE.md to render the current phase status, retry information, and recent decisions.

What is the best way to monitor retry information across planning and execution stages?▼

Monitoring retry information is done by parsing the STATE.md file within the .planning directory, which provides structured status views for each phase and recent workflow decisions.

How do I view recent decisions and current state for a specific quest phase?▼

Viewing recent decisions and current state requires parsing the PHASES.md and STATE.md files in the .planning directory to output structured phase status and retry details.

Do I need a .planning directory to check my quest status?▼

Yes, you need a .planning directory containing the QUEST.md, PHASES.md, and STATE.md files, as the status script parses these specific files to render the current workflow progress.

Can I use quest status reporting without any external dependencies?▼

Yes, you can use quest status reporting without external dependencies, as it relies solely on internal shell scripts and local markdown files to parse and display the current workflow state.