Skip to Content
Cheat Sheet/test-feature

/test-feature

Launch the quality-engineer agent to draft a comprehensive test plan for a feature, or to execute validation against an existing specification — the discipline that catches what unit tests miss.

When to use it

Run this when a feature is implemented and you want a structured validation pass before calling it done — beyond the per-PR test coverage that lands with the implementation ticket. The quality-engineer agent reads the feature’s acceptance criteria, identifies the test surface (happy path, edge cases, error conditions, integration boundaries), produces a test plan, and (if asked) executes the plan against the live feature, reporting PASS / FAIL per test case with reproduction steps.

The standard project flow has per-PR tests landing in CI. This command operates above that level — for cross-cutting features that span multiple PRs, for user-facing flows that benefit from end-to-end validation, and for releases that need a green sign-off across the whole feature set. The quality-engineer thinks in scenarios, not in unit tests.

Don’t run this as a substitute for per-PR test coverage. Tests that catch a regression in CI are the cheapest place to catch it. This command is the second-pass validation, not the first.

How it fits

Inputs are the implemented feature and its acceptance criteria. Outputs are a test plan and (on execution) a PASS / FAIL report that feeds /release-decision or produces fix tickets via /create-ticket.

What it does (quick)

  • Reads the feature spec (acceptance criteria from linked tickets, architecture doc context, PRD requirements)
  • Identifies test surface — happy path, edge cases, error conditions, integration boundaries
  • Produces a structured test plan with scenario-level test cases
  • Optionally executes the plan against the live feature, reporting PASS / FAIL per case with reproduction steps for failures
  • Outputs the report in a form /release-decision can consume
  • /work-ticket — upstream; per-PR test coverage is the first-pass validation this command builds on
  • /release-decision — downstream; consumes the validation report as evidence for the ship/wait decision
  • /create-ticket — the natural follow-up when validation surfaces fix-worthy gaps

Canonical spec: .claude/commands/test-feature.md

Last updated on
/architect-review/release-decision