The outcome

Produce a reviewed feature whose implementation, tests, and changes trace back to an accepted specification.

Step by step

A workflow you can repeat.

  1. 01

    Define the user outcome, acceptance criteria, architecture constraints, privacy boundary, non-goals, and trusted validation commands.

  2. 02

    Create a new Quest in a Git worktree, select Agent and Spec-driven mode, and attach only the files and repository knowledge needed.

  3. 03

    Review the generated Spec, plan, rules, memory, skills, plugins, and proposed tools, resolving product and security decisions before execution.

  4. 04

    Monitor steps and terminal output, reject unnecessary sandbox escalation, and inspect or reject each changed file in the Review panel.

  5. 05

    Run the real project checks independently, compare behavior with every requirement, and open a peer-reviewed change without granting autonomous push or deploy authority.

Working standard

What good use looks like.

  • Use worktrees for autonomous tasks.
  • Review the Spec before execution.
  • Reject unnecessary sandbox escalation.

Official references

Check the current product documentation.