Use when a prompt begins with an UPPERCASE action token (BACKGROUND / REMINDER / ISSUE / BUG / TASK / a sub-system name) in any of the six §11.4.140 forms — NAME :: rest, PREFIX::NAME :: rest, /NAME rest, /PREFIX::NAME rest, NAME ---> rest, or the single-colon NAME: rest — or when the operator asks how the…
Validates media files (MP4, PNG, TXT) by running OCR, metadata checks, and pattern matching against expected content, returning PASS/FAIL with captured evidence. Use when a task needs to verify a recording, screenshot, or text-evidence file actually contains an expected pattern before a PASS is claimed — the…
Automatic multi-track ruler orchestration per §11.4.187 — one conductor session spawning, driving, resuming, monitoring and controlling per-track headless workers with per-subscription auth, rate-limit rebind and crash-resilient supervision. Use when working with parallel development tracks, per-track headless…
Use whenever anything trackable is reported or discovered — a bug, a defect, a regression, a feature request, an internal task, a gap, "this is broken", "we should add X", "remember to do Y" — or when the operator invokes /issue, /bug, /task (or their /helix: and /default- forms, or the ISSUE/BUG/TASK action…
Teaches an agent to record background/deferred work via the scheduled-work MCP server and — before ever reporting it done — to verify uncertain, blocked, or overdue items against real captured evidence. Use when dispatching background work, when a REMINDER fires and unconfirmed work must be re-checked, or before an…
Syncs Claude Code project data — memories, session transcripts, settings, agent definitions, remember-logs, and handoff documents — between the same project on a remote workstation and the local machine over SSH, so local work can resume exactly where a remote session left off. Use when starting on a new machine…
Use when moving a tracked item through its lifecycle — starting work, marking it ready for testing, closing it, reopening it, marking it obsolete or operator-blocked — or when asked which Status/Type value is legal, how to close a Feature vs a Bug, why the Issues/Fixed docs must be regenerated rather than hand-edited…
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
★not rated 2 2d agoA28 tokens
copy · 75%MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: