Quest Creation

  1. Overview
  2. Hand Off Documentation
  3. Diagnose (Project Setup)
  4. Quest Creation

Feature Owner: Mich Tapawan → James Derick Billate
Module: Diagnose (Project Setup)
Priority: Must
Date: July 8, 2026

Executive Summary

What is this feature?

Quest Creation allows Creators to digitally create and curate quest content. It provides the starting workflow for initiating a quest through either manual creation or AI-assisted creation, instead of relying on multiple separate tools to organize learning content.

Why does it matter?

Without Quest Creation, Creators would need to manually initialize quest ideas and manage content across multiple software tools. This slows down how quickly content ideas can be structured and presented to learners. With Quest Creation, WyzQuests gives Creators a focused and efficient way to prepare quests for learner delivery.

What's the MVP scope?

  • Quest information input.

  • AI Assistant creation flow.

  • Manual creation flow.

  • Quest mode selection: Narrative (Linear) or Exploration (Branching).

  • Optional quest profile image support.

1. User Pain Point & Solution

John wants to create his own quest, but he currently does it manually or through multiple software tools. As more quests are created, this becomes inefficient and increases the risk of disorganized content. Quest Creation gives John a single workflow where quest details, goals, and delivery mode can be captured in WyzQuests.

Pain Points

  • Emotional: Tired, confused, and exhausted from managing quest setup manually.

  • Functional: Possible risk with data integrity and disorganization of information or files.

  • Business: More learners will be able to access the quest idea easily and efficiently once the content is created inside the platform.

2. 4D Framework Mapping

Diagnose: Provides a digital way to create and curate quests for learners without the need for excessive manual effort.

Design: Generates a structured and organized plan for quest content.

Develop: Further enhances the quest idea and guides Creators with quest goals, learning objectives, and selected quest mode.

Deliver: Provides a more efficient way to deliver quality quests by ensuring organized information through digital means.

3. USER FLOWS

Entry Points: Creator must be logged in with their specified account.

Success Criteria: Once the Creator navigates to the dashboard, selects Create Content, chooses Quest, and applies the necessary choices, the quest creation form or AI Assistant workflow must be displayed and able to create a quest record.

Main Path (Happy Path)

  • Sign in as a Creator.

  • Click Create Content.

  • Choose Quest.

  • Choose AI Assistant or Manual.

  • Choose quest mode: Narrative or Exploration.

  • Input necessary quest information.

  • Submit the form.

  • System validates the input.

  • System creates the quest record in Supabase.

  • System redirects or displays the created quest for continued editing.

No Data: Alert the Creator that required quest information is missing or incomplete.

API Error: Terminate the quest creation process promptly and display the proper error codes and messages.

Permission Denied: Do not process quest creation for non-Creator accounts or accounts without valid creator access.

Decision Points:

  • IF quest creation is processed successfully THEN insert the record into the database ELSE halt the quest creation process.

  • IF manual creation is selected THEN show the manual quest input form ELSE launch the AI Assistant flow.

  • IF quest mode is Narrative THEN save quest_mode = "linear" ELSE save quest_mode = "exploration".

  • IF validation fails THEN return Zod validation errors and keep the Creator on the form.

4. Information Architecture

Primary Information

  • Quest title.

  • Quest introduction.

  • Quest description.

  • Quest mode: Narrative or Exploration.

  • Duration.

  • Tags.

  • Skills.

  • Learning objectives

Secondary Information

  • Text guide for creation choices and input fields.

  • Optional quest profile image.

  • Creation mode: AI Assistant or Manual.

Tertiary Information

  • Draft publishing status.

  • Creator or agency ownership context.

Actions

  • Primary CTA

    • “Create Content”

  • Secondary Actions

    • AI Assistant.

    • Manual.

    • Create.

    • Cancel.

5. Data Requirements

Frontend Needs

  • Creator account information.

  • Quest information to be inputted.

  • Quest mode selection.

  • Text guide for choices and input fields.

  • Optional image file for quest profile.

API Calls Frontend Will Make

  • POST /api/creator/(content)/create-quest

  • POST /api/creator/(content)/batch-create-quests

  • GET /api/creator/(content)/list-quests

  • PATCH /api/creator/(content)/update-quest

6. Performance Considerations

Database Optimization

No major optimization is needed because this feature is primarily for inserting quest records. Supabase queries should still select only the required columns, especially when listing quests on the Creator dashboard.

7. Security & Authorization

Who Can Access This Feature?

Administrator: No access.
Reviewer: No access.
Creator: Full access.
Learner: No access.
Agency Admin: No access.

8. Error Handling

Current Existing Error Handling

  • Invalid credentials return an authentication error.

  • Incorrect or missing input returns a Zod validation error.

  • Unauthorized users cannot create a quest.

  • Invalid quest mode returns a validation error.

  • Database insert failures return an internal server error.

  • Failed optional image upload returns an upload error and should not silently corrupt the quest record.

9. Testing Checklist

Happy Path

  • Sign in as a Creator.

  • Click Create Content.

  • Choose Quest.

  • Choose AI Assistant or Manual.

  • Choose Narrative or Exploration.

  • Input necessary information.

  • Submit the form.

  • Confirm the quest is created and visible in the dashboard.

  • Confirm quest_mode is saved correctly.

Edge Cases

  • Unauthorized account.

  • Missing required input.

  • Invalid quest mode.

  • Duplicate or invalid quest title where applicable.

  • Optional image upload failure.

  • Internal server error if the quest does not push through in the database.

10. OPEN QUESTIONS

  • Should there be a multiple-page quest creation form to make the process more interactive and organized?

  • Should AI Assistant creation require a review step before inserting the generated quest?

11. OUT OF SCOPE

  • Advanced multi-page creation wizard beyond the current creation flow.

  • Learner-facing quest player behavior.

  • Advanced publishing, review, and approval workflow.

12. SUCCESS METRICS

  • Quest is successfully created.

  • Quest is saved with the selected quest mode.

  • Creator can continue editing the created quest.

  • Creator can find the quest in the dashboard or content list.

18. DEPENDENCIES

This feature depends on

  • Clerk Authentication.

  • Creator account details.

  • Supabase Database.

  • Quest schema validation.

This feature depends on this

  • Project Creation

19. TIMELINE & OWNERSHIP

Backend: Mich Tapawan

Frontend: Mich Tapawan

QA: Internal development testing

Estimated Completion: Feature completed.

Note: API Endpoints and Schema please refer to its Technical Documentation

Written by James Derick Billate Last updated July 14, 2026
Was this article helpful?