Menu
Read tickets, post test result comments, and change ticket status as part of the QA gate on the Planning Board.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Participate in team discussions, report quality patterns, and respond to mentions on the Meeting Board.
Read review queue, post review feedback, and transition tickets through the CQ gate on the Planning Board.
Post status updates, respond to mentions, and communicate with the team on the Meeting Board.
Read assigned tickets, post comments, and update ticket status on the Planning Board.
Post deployment status, infrastructure health updates, and coordinate with team on the Meeting Board.
Read tickets, post deployment comments, and move tickets to closed status on the Planning Board.
| name | planning-board |
| description | Read tickets, post test result comments, and change ticket status as part of the QA gate on the Planning Board. |
QA has gate permissions on the planning board. You are authorized to read tickets, post detailed test result comments, and change ticket status as part of the QA gate in the pipeline.
Note: Tickets have both a priority (1-5 categorical importance) and a rank (backlog position managed by PO). QA does not modify rank.
| Action | Allowed | Notes |
|---|---|---|
| GET tickets | Yes | Filter by status, read all fields |
| POST comments | Yes | Detailed test results on any ticket |
| PUT status | Yes | in-qa -> rfp (pass), in-qa -> in-progress (fail) |
| POST tickets | No | Cannot create tickets |
| DELETE tickets | No | Cannot delete tickets |
| PUT assignee | No | Cannot assign tickets |
curl -s "${PLANNING_BOARD_URL}/api/tickets?status=in-qa" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json"
Returns all tickets currently in the in-qa status. Process them oldest first based on the updated_at or moved_at timestamp.
curl -s "${PLANNING_BOARD_URL}/api/tickets/${TICKET_ID}" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json"
Returns the full ticket including description, acceptance criteria, comments, history, and current status.
curl -s -X POST "${PLANNING_BOARD_URL}/api/tickets/${TICKET_ID}/comments" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"author": "qa",
"type": "qa_pass",
"body": "## QA PASS\n\nAll acceptance criteria verified:\n\n- [x] Criterion 1: Verified - [details]\n- [x] Criterion 2: Verified - [details]\n- [x] Criterion 3: Verified - [details]\n\nTicket is ready for production."
}'
curl -s -X POST "${PLANNING_BOARD_URL}/api/tickets/${TICKET_ID}/comments" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"author": "qa",
"type": "qa_fail",
"body": "## QA FAIL\n\n### Failed Criteria\n- [ ] Criterion 2: FAILED\n\n### Steps to Reproduce\n1. Start from clean state\n2. Navigate to [location]\n3. Perform [action]\n4. Observe [result]\n\n### Expected Behavior\n[What the acceptance criteria specifies should happen]\n\n### Actual Behavior\n[What actually happened, with specifics]\n\n### Severity\n[Critical | Major | Minor]\n\n### Passing Criteria\n- [x] Criterion 1: Verified\n- [x] Criterion 3: Verified"
}'
curl -s -X PUT "${PLANNING_BOARD_URL}/api/tickets/${TICKET_ID}/status" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"status": "rfp",
"changed_by": "qa"
}'
curl -s -X PUT "${PLANNING_BOARD_URL}/api/tickets/${TICKET_ID}/status" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"status": "in-progress",
"changed_by": "qa"
}'
CRITICAL: When failing a ticket, you MUST execute BOTH the comment POST and the status PUT. This is the Quinn Rule. A comment without a status change leaves the ticket stranded in in-qa and stalls the pipeline.
rfpin-progress (THE QUINN RULE - both are mandatory)