skills.rest
findexu
findexuCOMMUNITY
Explore all skills by this author →
GitHub

quest-system

Manage feature development as quests with persistent scroll-based memory.

1|Updated May 27, 2026
Search Tags:#feature planning#decision logging#persistent context#quest management#risk tracking#expedition workflow
One-click install
npx skills add https://github.com/findexu/finpack-claude --skill quest-system-findexu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quest-system
Source: https://github.com/findexu/finpack-claude/tree/main/plugins/setup-finpack/template/skills/quest-system
Command: npx skills add https://github.com/findexu/finpack-claude --skill quest-system-findexu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quest System prevents Claude Code context from getting lost by maintaining a persistent, scroll-based memory of decisions, dangers, and expedition history across feature development.

Core Features & Use Cases

  • Quest/Expedition management: Track each feature as a quest and each work loop as an expedition, with a clear “road ahead” for what’s next.
  • Persistent scroll state: Keep five structured scrolls (WORLD_MAP, STRATEGY_SCROLL, ADVENTURE_JOURNAL, TOME_OF_DANGERS, ADVENTURERS_HANDBOOK) so knowledge survives across conversations.
  • Guardrails & safety hooks: Enforce “never rely on conversation history,” record fallen strategies, and maintain an institutional DANGER_REGISTRY and DECISIONS_LOG at the project level.

Quick Start

Run /new-quest to create your quest and then use /start-quest to get guided to the next step.

Frequently Asked Questions about quest-system

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

FAQPage Schema
How do I maintain persistent context for feature planning across repeated Claude Code sessions?▼

Persistent context for feature planning is maintained by structuring work as quests and expeditions, using scroll-based memory files like WORLD_MAP and STRATEGY_SCROLL to preserve decisions and strategy history across repeated sessions.

How do I track risks and decision logging during mono-repo feature development?▼

Risk tracking and decision logging during mono-repo feature development are handled by maintaining a project-level DANGER_REGISTRY for institutional risks and a DECISIONS_LOG to record fallen strategies and choices across multiple app targets.

Can I use quest management to coordinate implementation sequencing across multiple app targets?▼

Yes, quest management coordinates implementation sequencing across multiple app targets by treating each feature as a quest and each work loop as an expedition, providing a clear road ahead for priority and task ordering.

What's the best way to start an expedition workflow for a new feature?▼

To start an expedition workflow for a new feature, run the /new-quest command to initialize the quest structure, then use /start-quest to get guided to the next required step in the implementation sequence.

Does quest management work without relying on conversation history for context?▼

Yes, quest management enforces guardrails that explicitly prevent relying on conversation history, instead using persistent scrolls and structured journals to ensure knowledge survives across sessions and commands.

Related Skills

Explore More Software Engineering Skills→
diadia0000diadia0000

quest

Track quest progress and manage milestones in game environments.

Community
Intermediate
greentcsolutions-labgreentcsolutions-lab

prompt-classifier

Classify Claude Code CLI prompts into intent categories with starter steps.

Community
Basic
rysweetrysweet
1

roadmap-strategist

Plan and optimize project roadmaps, goals, milestones, and strategic direction.

Community
Basic
sayujks0071sayujks0071
1

trading-strategy-development

Implement OpenAlgo trading strategies with risk management and backtesting scaffolding.

Community
Advanced