Skip to main content
command CX Codex

qa — Claude Code command: what it does, how to install

qa runs the app you already have up through scenarios taken from the spec, then gives a verdict on what a real user would hit.

MIT ★ 730 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next
Open on GitHub

What qa does

The command is mostly a hand-off. Whatever you pass in goes to the flow-next-qa skill, and that skill does the work: it resolves the spec, derives scenarios from it, drives the running app through flow-next-drive, files what it finds and returns a verdict.

The argument hint is <fn-N>. Automatic model invocation is off, so you start it yourself. All the logic sits in the skill, which makes the command an empty shell without flow-next-qa installed.

On Claude it arrives with the flow-next plugin. Codex keeps the same prompt at ~/.codex/prompts/qa.md.

What it helps with

  • run a fresh build against spec scenarios before shipping
  • catch where the live app drifts from what the spec says
  • get a verdict on one <fn-N> item instead of a vague “seems fine”
  • have findings filed as items rather than scattered notes
  • hand a manual feature check to the agent without writing the steps

Example prompts for the agent

  • /qa fn-4 — walk the running app through the spec scenarios for fn-4 and tell me what breaks.
  • Run /qa fn-9 and file everything you find.
  • Check /qa fn-2 against the build that is already up.

How to install qa

1Plugin marketplace

/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-next

2Manually: put the files in place

.claude/commands/qa.md

Call it with /qa. For all projects use ~/.claude/commands/

Questions about qa

How do I install qa in Claude Code?

Add the marketplace with /plugin marketplace add gmickel/flow-next, then run /plugin install flow-next@flow-next. The command comes with the plugin.

What does qa do?

It hands your argument to the flow-next-qa skill, which reads the spec, derives scenarios, drives the live app and returns a verdict.

Does qa work in Codex?

Yes. The prompt file goes to ~/.codex/prompts/qa.md, and the <fn-N> argument works the same way.

Source text

qa.md · MIT
---
name: qa
description: Live-app real-user QA pass derived from the spec
argument-hint: "<fn-N>"
disable-model-invocation: true
---

# IMPORTANT: This command MUST invoke the skill `flow-next-qa`

The ONLY purpose of this command is to call the `flow-next-qa` skill. You MUST use that skill now.

**Arguments:** $ARGUMENTS

Pass the arguments to the skill. The skill handles spec resolution, scenario derivation from the spec, driving the live app via flow-next-drive, finding-filing, and the verdict.

© Gordon Mickel · MIT · gmickel/flow-next

Similar slash commands

All slash commands for Testing and QA →

From the same set70

The whole set →

Project sponsors

Companies that keep this analytics open