qa-new-flow
You are creating a new browser QA flow spec in qa/browser-flows.
Args: $ARGUMENTS
If no args or --help is present, print usage and stop.
Usage:
/qa-new-flow --id=flow-id --title="Short title" --resources=assistant-settings,conversation-rules --goal="What it verifies"- Optional:
--parallel-safe=true --conflicts-with=other-flow-id,another-flow-id --preconditions="Signed in" --cleanup="Remove test rule"
Steps:
- Collect required fields (
id,title,resources).- If any are missing, ask the user for them before proceeding.
- Ensure
idis a URL-safe slug (lowercase, numbers, dashes only) and matches the filename. - Create
qa/browser-flows/<id>.mdusingqa/browser-flows/_template.mdas a base. - Replace the template front matter with the provided values.
- If optional fields are provided (
parallel_safe,conflicts_with), include them in the front matter.- Always serialize
conflicts_withas a YAML list by splitting the--conflicts-withvalue on commas (even for a single id).
- Always serialize
- If
--goalis provided, replace the Goal section placeholder with it. - If
--preconditionsis provided, replace the existingPreconditionssection placeholder list with those items. - If
--cleanupis provided, replace the Cleanup section placeholder with it. - Leave the other section bodies as editable placeholders if the user does not provide step details.
- Confirm the file path and next steps to edit the flow.
Do not overwrite an existing flow file without explicit confirmation.
More from elie222/inbox-zero
ui-components
UI component and styling guidelines using Shadcn UI, Radix UI, and Tailwind
77security
Security guidelines for API route development
36fullstack-workflow
Complete fullstack workflow combining GET API routes, server actions, SWR data fetching, and form handling. Use when building features that need both data fetching and mutations from API to UI.
23test-feature
End-to-end feature testing — browser QA, API verification, eval tests, or any combination. Covers browser interactions (via agent-browser CLI), Google Workspace operations (gws CLI), API calls, and LLM eval tests. Can also persist tests as reusable QA flows or eval files.
21testing
Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features
21project-structure
Project structure and file organization guidelines
21