qa-agent

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Turn ticket requirements into a concrete, ticket-native QA test case set before implementation.

在开发前将工单需求转化为具体的、原生的QA测试用例集。

Read
```
/orchestra-config.json
```
from the repository root before starting.
Read
```
issue_tracker
```
and use only the configured tracker MCP for ticket operations.
Use the MCP mapped to
```
issue_tracker
```
in
```
orchestra-config.json
```
.
If the configured issue tracker MCP is unavailable, stop immediately and do not proceed with the task.
For every created subtask/comment/tag/status update, include:
```
Skill-Version: qa-agent@1.1.0
```
.

Parent issue ID (source of truth ticket)
Functional requirements in the ticket
Technical requirements and constraints from the tracker subtask tagged
```
technical-details
```
Acceptance criteria and business context in the ticket

A new subtask under the parent issue, tagged
```
qa-plan
```
Test cases written directly in that QA subtask, including:
Positive path cases
Edge and failure cases
Non-functional checks relevant to ticket scope
Clear pass/fail expectations per test case
Parent ticket comment linking the QA subtask and confirming QA planning completion in 1-2 lines

Read
```
/orchestra-config.json
```
from the repository root, set the issue tracker context, and verify the configured tracker MCP is available.
Read the parent issue only (description, acceptance criteria, comments, labels, linked requirement notes).
Find and read the child subtask tagged
```
technical-details
```
; use it as the source for technical constraints.
Translate ticket requirements into explicit testable behaviors.
Draft comprehensive test cases for happy path, edge cases, failure modes, and scope-relevant non-functional checks.
Create a subtask titled
```
QA Plan: <parent issue title>
```
and apply tag
```
qa-plan
```
.
Add the test cases to the QA subtask as structured checklist items or clearly separated sections.
Add a concise parent-issue comment linking the QA subtask and hand off to
```
pre-implementation-agent
```
.
Add a tag qa-plan-created to the parent ticket.

Do not rewrite product scope.
Flag ambiguity as open questions in tracker comments instead of guessing. Add Tag open-qa-questions to the parent ticket.
Separate must-pass checks from optional hardening checks.
Do not create
```
QA_PLAN.md
```
or any external QA artifact.
Do not read repository code or architecture documents for QA planning.
If no subtask with tag
```
technical-details
```
exists, add a blocking comment on the parent ticket and stop.
If ticket scope and requirement details conflict, log mismatch in the tracker before proceeding.
Do not run tracker operations unless the MCP for the configured
```
issue_tracker
```
is available.
Keep tracker comments concise and avoid repeating the full QA test list in parent comments.

Add tag read-for-pre-implementation to the parent ticket. And change status to TODO.

为父工单添加

read-for-pre-implementation

标签，并将状态改为TODO。