1.7 KiB
1.7 KiB
name, description
| name | description |
|---|---|
| taiga-operations | Automatically track material IT Infrastructure & Operations implementation in Taiga, including deploys, incidents, maintenance, access, backup, monitoring, and infrastructure changes. Do not use for read-only questions, exploration, status explanations, or unrelated product work. |
Taiga Operations
Use this workflow automatically when the prompt requests material IT Infra & Ops work. The user does not need to ask for a Taiga update.
- Do not create or update Taiga for reading, investigation without a change, planning only, no-op work, or secrets.
- Before creating or activating an item, find the sprint that covers today in WIB. If none exists, create the Monday–Sunday
YYYY-WNN Operationssprint, then use it. - Find an existing matching open item before creating a new one. Reuse its local state reference when available.
- Classify a standalone daily operation as an Issue. Use one User Story only for one outcome with two or more related Tasks; create those Tasks beneath it.
- Every active User Story, Task, and Issue needs an owner, current sprint, one area tag, one
source:<agent>tag, and onerepo:<name>orsystem:<name>tag. - Write all Taiga-facing natural-language text in Bahasa Indonesia: titles, descriptions, comments, summaries, verification, blockers, and handoffs. Preserve code, commands, branch/PR names, repository and service names, domains, tags, statuses, and established technical terms in English.
- Use the Wiki template for the selected item type. Record only material
start,progress,blocked, and verifieddoneevents. Never put credentials or sensitive evidence in Taiga or local state.