How To Use Workflows

Basic Prompt Pattern

A simple pattern works well: describe the task, then name the workflow you want.

Use direct prompts such as Use the plan workflow before editing, Handle this as debug, or Do a review of the current branch.

Use the plan workflow before making changes.
Use the debug workflow to isolate the root cause.
Use the review workflow on the current branch.

When To Use Which Workflow

• brainstorm: the request is still vague and you need options or tradeoffs.
• plan: you want a task breakdown before implementation.
• create: the request is concrete and ready to implement.
• enhance: you are extending or refining existing behavior.
• debug: there is a bug, regression, or unclear runtime behavior.
• review: you want findings on a patch, branch, or design.
• check: you want fast validation after a normal code change.
• test: the main task is writing or running tests.
• verify: the change is release-sensitive or cross-cutting.
• preview: you want to start, fix, or verify a local preview.
• deploy: you are preparing or executing a deployment.
• status: you want a concise snapshot of current repository state.
• orchestrate: multiple bounded subagents are justified.
• ui-ux-pro-max: the task is primarily UI direction or UX shaping.

Copy-Paste Examples

Brainstorm 3 realistic approaches for adding auth to this app.

Use the plan workflow and break this change into concrete implementation steps.

Use create to implement this feature in the current repo.

Use debug to find the root cause of this failing login flow before changing code.

Use review on the current branch and focus on correctness, regressions, and missing tests.

Use verify before we ship this release candidate.