game-quest

To create coherent game quests, you need a framework that checks narrative consistency against existing world lore. This skill designs quests with objective trees and briefs while integrating with your world lore documentation to ensure narrative alignment. It requires up-to-date lore and registry files to function properly.

Quest registry management is the process of organizing and tracking quest data for easy reference and updates. It is needed for game design to maintain consistency across multiple quests, prevent narrative conflicts, and ensure that new quests align with previously established objectives and world lore.

You structure game quest objectives by using a design framework that builds objective trees and prepares design briefs. This skill provides that structured approach, allowing you to define clear quest goals, verify narrative coherence, and document the gameplay experience before implementation.

Yes, you need specific documentation files to design quests end-to-end. You must maintain up-to-date `docs/world-lore.md` and `docs/quest-registry.md` files, as this skill relies on these documents to check for narrative coherence and manage quest data within the registry.

No, you cannot use this quest creation skill without other game design dependencies. Full functionality requires related skills like `quest-narrative-coherence` and `quest-mission-design` to properly check narrative alignment and define detailed mission objectives.

The best way to ensure narrative coherence when designing a game quest is to run automated coherence checks against your existing world lore documentation. This skill integrates directly with your lore files to verify consistency and generate briefs that fit seamlessly into the established narrative.