Prompts.en

# Example Workflows and Prompts

These are routing examples, not scripts to paste blindly. Adapt them to your repository, naming, and toolchain.

## Clarify a vague idea before coding

- "/plan Design a public setup guide for this repository. Ask clarifying questions first and write PLAN.md."
- "/plan Compare two ways to structure the verification workflow here, then produce acceptance criteria and implementation steps."

Expected owner: `/plan` on `plan-deep`

## Turn the plan into test anchors

- "/spec Generate Vitest skeletons for the acceptance criteria in PLAN.md."
- "/spec Create test cases for the next unchecked step in PLAN.md."

Expected owner: `/spec`

## Implement against the plan

- "/implement Work through the next unchecked step in PLAN.md."
- "/implement Continue the workflow docs migration without drifting from the acceptance criteria."

Expected owner: `build` or `build-deep`

## Use deep implementation mode only when it pays off

- "Switch to build-deep and implement the riskiest migration step."
- "Use build-deep for the refactor, but keep the change scoped to the current acceptance criteria."

## Review and verify explicitly

- "/review Review the staged workflow docs changes for confusing guidance or regressions."
- "/verify Run the repo checks and explain any failures."

## Bring runtime evidence into the loop

- "Check whether this workflow claim is contradicted by recent Sentry issues."
- "Look at unresolved production errors before we finalize the docs guidance."

Expected overlay: Sentry MCP

## Pull in optional extensions only when they add distinct value

- "Use OpenSpec only if we need persistent change artifacts beyond PLAN.md."
- "Load a framework-specific skill only if the task clearly matches that framework."

## Good prompt habits

- say whether you want planning, test design, implementation, review, or verification
- name the relevant files or modules when you know them
- include constraints and success criteria
- ask for trade-offs when the decision is still open