메뉴
Read tickets, post deployment comments, and move tickets to closed status on the Planning Board.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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.
Communicate with human stakeholders via Meeting Board, Discord, or Slack webhooks.
| name | planning-board |
| description | Read tickets, post deployment comments, and move tickets to closed status on the Planning Board. |
OPS has deployment-gate permissions on the planning board. You are authorized to read tickets, post deployment comments, and move tickets to their final closed status after successful deployment.
Note: Tickets have both a priority (1-5 categorical importance) and a rank (backlog position managed by PO). OPS does not modify rank.
| Action | Allowed | Notes |
|---|---|---|
| GET tickets | Yes | Filter by status, read all fields |
| POST comments | Yes | Deployment details on any ticket |
| PUT status | Yes | rfp -> closed (after successful deployment) |
| 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=rfp" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json"
Returns all tickets with status rfp (Ready for Production). These have passed both CQ review and QA testing.
curl -s "${PLANNING_BOARD_URL}/api/tickets/${TICKET_ID}" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json"
Returns the full ticket including all comments from DEV, CQ, and QA. Review these for deployment context.
curl -s -X POST "${PLANNING_BOARD_URL}/api/tickets/${TICKET_ID}/comments" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"author": "ops",
"type": "deployment",
"body": "## Deployment Complete\n\n**Deployed:** [service/component name]\n**Environment:** [production/staging]\n**Timestamp:** [ISO timestamp]\n**Version/Tag:** [version or commit hash]\n\n### Deployment Steps Executed\n1. [Step performed]\n2. [Step performed]\n3. [Step performed]\n\n### Post-Deployment Verification\n- [x] Health checks passing\n- [x] Smoke tests passing\n- [x] Monitoring dashboards nominal\n- [x] Error rates within threshold\n\n### Rollback Plan\nTo rollback this deployment:\n1. [Rollback step]\n2. [Rollback step]\n3. [Verify rollback step]\n\n**Status: Successfully deployed and 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": "closed",
"changed_by": "ops"
}'
curl -s -X POST "${PLANNING_BOARD_URL}/api/tickets/${TICKET_ID}/comments" \
-H "Authorization: Bearer ${AGENT_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"author": "ops",
"type": "deployment_failed",
"body": "## Deployment Failed\n\n**Attempted:** [timestamp]\n**Environment:** [production/staging]\n\n### Failure Details\n[What went wrong during deployment]\n\n### Actions Taken\n1. [Rollback executed / not needed]\n2. [Systems verified stable]\n\n### Root Cause\n[Initial assessment of what caused the failure]\n\n### Next Steps\n[What needs to happen before re-attempting deployment]\n\n**Status: Deployment halted. Ticket remains in rfp pending resolution.**"
}'
rfp