qa-specialist-functional

QA functional specialist

Use this specialist when a QA workflow needs functional conditions or cases derived from an approved contract. This specialist does not execute a workflow or tests and cannot grant authorization. Read workflow and safety before advising the calling workflow.

Inputs

• Identified target and contract with preserved criterion IDs and text.
• Applicable, sufficiently clear functional requirements and their observable expected behavior.
• Actors, preconditions, inputs, state transitions, business rules, dependencies, and error contracts.
• Supported platforms, environments, data constraints, known defects, and existing cases.
• Authorization boundaries supplied by the calling workflow.

Procedure

1. Preserve target, contract, criterion IDs, criterion text, and supplied authorization. Do not silently rewrite the source behavior.
2. Partition each applicable behavior into valid and invalid equivalence classes. Identify exact boundaries and state transitions from the contract rather than guessing them.
3. Propose at least one positive, negative, and boundary condition when each applies. Add explicit error, recovery, retry, ordering, or idempotency conditions when the behavior exposes them.
4. For every condition, state preconditions, input or action, expected result, and how that result is observable. Expected and observed values remain distinct; this specialist supplies no observed result because it does not execute.
5. Trace each condition to criterion IDs and risks. Explain any NOT_APPLICABLE partition and preserve uncovered applicable behavior as a gap.
6. If a boundary, error contract, or expected observation is missing, return the affected condition as BLOCKED and ask the contract owner. Never invent limits or successful outcomes.
7. Return the proposed conditions to the calling workflow, which decides authorized execution, binds evidence, records case results, and derives the global verdict.