From b56f7def02c04f60eaf49f99810020abd6778a7b Mon Sep 17 00:00:00 2001 From: Adnan Zahir Date: Sat, 29 Aug 2026 19:35:45 +0700 Subject: [PATCH] Enforce Taiga active item governance --- plugins/taiga-auto-sync/.codex-plugin/plugin.json | 12 +++++++----- plugins/taiga-auto-sync/hooks/taiga-reminder.sh | 6 +++++- 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/plugins/taiga-auto-sync/.codex-plugin/plugin.json b/plugins/taiga-auto-sync/.codex-plugin/plugin.json index c049c08..71b4af7 100644 --- a/plugins/taiga-auto-sync/.codex-plugin/plugin.json +++ b/plugins/taiga-auto-sync/.codex-plugin/plugin.json @@ -1,18 +1,20 @@ { "name": "taiga-auto-sync", - "version": "0.1.0", - "description": "Injects Taiga tracking rules on every Codex prompt.", + "version": "0.1.0+codex.20260829123342", + "description": "Injects mandatory sprint, owner, and tag guards on every Codex prompt.", "author": { "name": "Local developer" }, "hooks": "./hooks/claude-codex-hooks.json", "interface": { "displayName": "Taiga Auto Sync", - "shortDescription": "Automatic Taiga tracking reminder.", - "longDescription": "Injects the IT Infra & Ops Taiga contract before each prompt.", + "shortDescription": "Taiga governance guard.", + "longDescription": "Guards active IT Infra & Ops work with a current sprint, owner, and required tags.", "developerName": "Local developer", "category": "Productivity", - "capabilities": ["Lifecycle hooks"], + "capabilities": [ + "Lifecycle hooks" + ], "defaultPrompt": "Help me use Taiga Auto Sync." } } diff --git a/plugins/taiga-auto-sync/hooks/taiga-reminder.sh b/plugins/taiga-auto-sync/hooks/taiga-reminder.sh index 37afac2..938d812 100755 --- a/plugins/taiga-auto-sync/hooks/taiga-reminder.sh +++ b/plugins/taiga-auto-sync/hooks/taiga-reminder.sh @@ -1,4 +1,8 @@ #!/bin/sh cat <<'EOF' -TAIGA AUTO-SYNC: For material IT Infra & Ops work, create or update the matching Taiga item now through the scoped launcher. Do not track read-only/no-op work. A new User Story must use the Wiki description template; preserve its state file for progress, blocked, and verified done updates. +TAIGA AUTO-SYNC GUARD: For material IT Infra & Ops work, use Taiga before implementation; do not track read-only/no-op work. + +Before creating or activating any User Story, Task, or Issue, resolve the sprint containing today in WIB. If none exists, create the Monday–Sunday `YYYY-WNN Operations` sprint first. Never leave an active item without its current sprint, an accountable owner, and one area, `source:`, and `system:` or `repo:` tag. + +Classify one standalone daily activity as an Issue; use a User Story only for one outcome with two or more related Tasks, and create Tasks beneath that Story. A new User Story must use the Wiki description template. Use the corresponding Wiki template for Task or Issue descriptions. Preserve per-item local state for progress, blocked, and verified done updates; do not put secrets in it. EOF