senkensha/infra-plugins
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Enforce Taiga active item governance

Browse Source
This commit is contained in:
Adnan Zahir
2026-08-29 19:35:45 +07:00
parent e4ad2e0475
commit b56f7def02
2 changed files with 12 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
plugins/taiga-auto-sync/.codex-plugin/plugin.json
View File

@@ -1,18 +1,20 @@
{ {
"name": "taiga-auto-sync", "name": "taiga-auto-sync",
"version": "0.1.0", "version": "0.1.0+codex.20260829123342",
"description": "Injects Taiga tracking rules on every Codex prompt.", "description": "Injects mandatory sprint, owner, and tag guards on every Codex prompt.",
"author": { "author": {
"name": "Local developer" "name": "Local developer"
}, },
"hooks": "./hooks/claude-codex-hooks.json", "hooks": "./hooks/claude-codex-hooks.json",
"interface": { "interface": {
"displayName": "Taiga Auto Sync", "displayName": "Taiga Auto Sync",
"shortDescription": "Automatic Taiga tracking reminder.", "shortDescription": "Taiga governance guard.",
"longDescription": "Injects the IT Infra & Ops Taiga contract before each prompt.", "longDescription": "Guards active IT Infra & Ops work with a current sprint, owner, and required tags.",
"developerName": "Local developer", "developerName": "Local developer",
"category": "Productivity", "category": "Productivity",
"capabilities": ["Lifecycle hooks"], "capabilities": [
"Lifecycle hooks"
],
"defaultPrompt": "Help me use Taiga Auto Sync." "defaultPrompt": "Help me use Taiga Auto Sync."
} }
} }

6
plugins/taiga-auto-sync/hooks/taiga-reminder.sh
View File

@@ -1,4 +1,8 @@
#!/bin/sh #!/bin/sh
cat <<'EOF' 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:<agent>`, and `system:<name>` or `repo:<name>` 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 EOF