Spec-Driven Mode is designed for complex, well-scoped tasks that require a clear technical plan, structured acceptance criteria, and a traceable record for team collaboration.
Scenarios
Use Spec-Driven Mode for tasks that meet the following criteria:
-
Feature development, bug fixes, and code refactoring.
-
Requires a clear technical solution and acceptance criteria before execution.
-
Involves multi-person collaboration or requires documentation retention.
Workflow
1. Clarify requirements
After you enter a task, Quest may ask clarifying questions in a multiple-choice format. Choose how to respond:
-
Recommend: Quest automatically selects the default answer and continues.
-
Continue: Select your own answer and continue.
-
Skip: Skip the question and go directly to chat.
2. Generate Spec
After you select the Spec-Driven scenario, Quest generates a structured Spec document with four sections:
-
Requirement description
-
Design solution
-
Task breakdown
-
Acceptance criteria
The Spec appears in the Spec Tab of the artifact area. It supports streaming output and download.
3. Review Spec
Before running the Spec, review and refine it:
-
Read the complete Spec in the Spec Tab on the right.
-
Refine the Spec through chat. You can adjust it anytime before clicking Run.
-
When satisfied, click Run Spec to start execution.
4. Monitor execution
While Quest executes the Spec, two panels keep you informed:
-
To-do list: Tracks real-time task progress in the Chat area.
-
Changed Files: Shows code changes in the Artifact area.
-
Append mid-process: Type additional requirements in the dialog box at any time. Quest adjusts the plan accordingly.
5. Accept results
After execution completes, apply or discard changes based on your mode:
-
Accept (Local mode): Apply all changes to the workspace.
-
Reject (Local mode): Discard all changes.
-
Apply (Parallel mode): Merge changes to the main branch.
-
Create PR (Remote mode): Create a pull request.