Problem
Quests currently don’t have a clear structure for numbering, timestamps, or re-application. Once a quest is completed, it’s not easy to review or run it again. This limits traceability and repeatability.
Solution
-
Add sequential numbers and timestamps to each quest.
-
Allow marking quests as re-review or re-implementation.
-
Provide options to re-run a single quest or sequentially re-run older quests.
-
Maintain an index (or overview page) to list quests, their order, status, and last execution.
How should it work?
-
When a new quest is created, it automatically receives a sequence number and timestamp.
-
Each quest has metadata (status, priority, scope).
-
Old quests can be executed again with the same or updated parameters.
-
A “batch replay” mode re-applies multiple past quests in sequence.
Use Case
-
Developer needs to re-run an older quest after a code change.
-
QA team wants to replay all quests from a sprint for regression testing.
-
A quest requires re-review before being applied with updated parameters.
Priority
High – Blocking issue: Missing ability to track and re-run quests.
Medium – Important improvement: Quest history becomes actionable.
Low – Nice to have: Index and batch replay for convenience.
Additional Info
-
File naming convention could include numbering and timestamps (
0001-20250930-title.md). -
Optional UI actions for “Re-run” and “Re-review.”