flow-next-qa SKILL.md skillA

flow-next-qa from gmickel/flow-next is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add gmickel/flow-next/flow-next-qa@git:20261031.ad77f16

Pins git:20261031.ad77f16 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

gmickel/flow-next

Path

plugins/flow-next/skills/flow-next-qa/SKILL.md

Versions recorded

14

Latest version

git:20261031.ad77f16, committed Oct 31, 2026

First version recorded

Jul 21, 2026

Size

4,365 bytes

Repository stars

718

License

MIT

Live-app real-user QA pass derived from the spec. Drives the running app via flow-next-drive, derives scenarios from the spec's AC / R-IDs / boundaries, files structured P0/P1/P2 findings with evidence, and ends with a YES/NO ship verdict receipt. Consumes `.flow/features/` navigation when present. Triggers on /flow-next:qa with a spec id. Runs user-invoked OR as the optional `pipeline.qa` stage of `flow --auto` (default off). Augments — never replaces — CI/staging/manual QA. FORBIDDEN from…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# /flow-next:qa — live-app real-user QA pass

Drive the running app the way an unforgiving real user would, with scenarios taken from the spec,
file P0/P1/P2 findings with captured evidence, and end with a YES/NO ship verdict written as a
`qa_verdict` receipt. The spec is the source of intent: acceptance criteria become scenarios,
R-IDs become the coverage table, boundaries say what not to test, decision context says what the
app should do.

QA is a cheap first live pass over the finished build. It does not replace CI, staging or manual
QA, and it does not fix product code: it files, surfaces and hands off. Findings are advisory; the
human reviewer and the land gate decide.

It runs when the user invokes it, or as the optional `pipeline.qa` stage (`off | on | auto`,
default `off`) that `/flow-next:flow` runs after all tasks are done and before make-pr. When
setting or reading that key, read [gate-selection.md](../flow-next-flow/references/gate-selection.md);
[`flowctl.md`](../../docs/flowctl.md) has the config row. Enable the stage only where
`/flow-next:prime` reports the app is QA-ready (seeded data, a documented dev login, a drivable
…

Read the whole file at its exact version.

How to install

mdr add gmickel/flow-next/flow-next-qa@sha256:4f5f6af45cb4a7c9

[![mdr](https://markdownregistry.com/badge/art_nnotdfaxlj4et4kv.svg)](https://markdownregistry.com/a/art_nnotdfaxlj4et4kv)

Versions

The registry has recorded 14 versions of this file, between Jul 21, 2026 and Oct 31, 2026, about one every 8 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_nnotdfaxlj4et4kv
GET https://markdownregistry.com/api/v1/resolve?ref=gmickel/flow-next/flow-next-qa
GET https://markdownregistry.com/api/v1/blob/4f5f6af45cb4a7c9a940b356f1cb6a853506b5c4aec04bcceeef4500632a3b6e

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from gmickel/flow-next

Every file in gmickel/flow-next

Other files named flow-next-qa

Browse by kind, by grade A, or by owner.