com um clique
quest-create
Create a new quest with phased execution plan
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
Create a new quest with phased execution plan
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Review open issues and PRs across aibtcdev repos with prioritized next steps
Evaluate session context through Arc's editorial lens and draft social posts
Create, update, and publish blog posts on arc0.me in Arc's voice
Generate daily summary of git activity across all repositories
Play Floor is Lava on Scrapyard arena as Arc (arc0btc). Interactive AI agent game on Stacks.
Mark the current quest as complete and archive it
| name | quest-create |
| description | Create a new quest with phased execution plan |
| allowed-tools | Bash, Read, Write, Edit, Glob, Grep, Task |
Create a new quest — a high-level goal broken into ordered phases for automated execution.
/quest-create <goal description or context>
The user provides a goal/prompt. The quest-planner agent derives a quest name and phase breakdown.
Check for active quests:
.planning/*/QUEST.md files with Status: active.planning/archive/ is always preservedSpawn quest-planner agent to analyze the goal:
Task tool with subagent_type: quest-planner
The planner returns:
Create quest directory: .planning/YYYY-MM-DD-<quest-name>/
Write quest files:
QUEST.md — Goal, linked repos, status (active), created datePHASES.md — Ordered phases, all status pendingSTATE.md — Current phase, activity logconfig.json — {"maxRetries": 3, "commitFormat": "conventional"}phases/ — Empty directory for phase plansAdd .planning/ to .gitignore if not already present
Display quest summary and next steps
# Quest: Quest Name
**Goal:** Goal description here.
**Status:** active
**Repos:**
- /path/to/repo (primary)
**Created:** YYYY-MM-DD
---
## Context
Detailed context from planner analysis.
## Key Dependencies
Phase dependency notes if any.
# Phases
## Phase 1: Name
Goal: What this phase achieves
Status: `pending`
## Phase 2: Name
Goal: What this phase achieves
Status: `pending`
Phase states: pending → completed (or checkpoint if stuck after maxRetries).
# Quest State
Current Phase: 1
Quest Status: active
## Activity Log
- YYYY-MM-DD: Quest created with N phases
{
"maxRetries": 3,
"commitFormat": "conventional"
}
.planning/
├── 2026-02-16-cost-tracking/
│ ├── QUEST.md
│ ├── PHASES.md
│ ├── STATE.md
│ ├── config.json
│ └── phases/
└── archive/
├── 2026-02-14-auth-system/
└── 2026-02-10-loop-hardening/
After creating a quest, use:
/quest-run to run the automated phase loop/quest-status to check progress