con un clic
list
Display all stored trigger phrases from .claude/triggers.json
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Display all stored trigger phrases from .claude/triggers.json
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Discover files with trigger_phrase and/or refresh frontmatter, let the user choose which to schedule for periodic re-injection via CronCreate. Prevents behavioral drift by keeping core rules and goals fresh in context.
Write trigger phrases from .claude/triggers.json into file frontmatter as model-scoped trigger_phrase fields. Bridges trigger generation (scan) with scheduled injection (zenflow:schedule).
Build a GitHub issue into a PR. User-launched with an issue number — reads the issue, confirms with user, creates branch, implements against acceptance criteria, runs verification, and opens a PR. Every decision surfaces via AskUserQuestion.
Collaborative working session — you and the user are a team exploring, researching, and planning together. When implementation work is needed, create well-structured GitHub issues. The user launches Builder agents to implement and Reviewer agents to verify.
Shed accumulated context mid-session. Writes a knowledge handoff document capturing session state, decisions, observations, and behavioral calibration, then guides the user through /clear and resumption.
Runtime verification using Playwright MCP + proof artifacts. Use when acceptance criteria mention UI behavior, when claiming runtime verification, or when independently verifying a PR's claims. Produces artifact-backed proof — screenshots, DOM snapshots — not prose claims.
| name | list |
| description | Display all stored trigger phrases from .claude/triggers.json |
| allowed-tools | Read |
Read .claude/triggers.json. If it doesn't exist, report "No triggers stored yet. Run /triggered:scan to generate some."
If the user provided a filter pattern (e.g., src/auth), only show entries whose file path contains that pattern.
Display as a formatted table:
File | Trigger Phrase | Confidence | Scanned
--------------------------- | ----------------------------- | ---------- | ----------
src/auth/middleware.ts | jwt route authentication guard | 0.90 | 2026-03-31
src/db/connection.ts | database connection pool mgmt | 0.85 | 2026-03-31
N triggers stored.