Use when the user wants to plan, dispatch, review or deploy software sprints in a multi-chat orchestration pattern — running parallel multi-agent work across isolated git worktrees without context bloat in long Claude sessions. Skill provides a portable workflow with auto-discovery of project profile, modular addons…
Agent Ops is the skill of managing and coordinating multiple agents to work together effectively. It involves assigning tasks, tracking progress, resolving conflicts, and ensuring that agents collaborate smoothly to achieve shared goals.
Use when starting a project, auditing an existing repo, planning a release, or writing project docs such as a spec, roadmap, release plan, engineering guide, changelog, or decision log. Provides a markdown-only, tool-neutral methodology for repo structure and living documentation.
A coordinator for complex, multi-stage projects that span conversations and tasks. It helps discuss requirements, create execution plans, assign roles, track progress, and preserve useful project knowledge.
Ingests open retro issues, investigates via scramstorm, dispatches scram team to address changes, bumps version, comments on issues, commits and pushes.
Create a well-formed JIRA issue in the AROSLSRE project with correct fields, labels, components, sprint assignment, and JIT documentation when applicable. For oncall investigations, creates a structured Story with sub-tasks for investigation, mitigation, and follow-up. Follows ARO HCP JIRA governance conventions.
Prioritize features, tasks, bugs, initiatives, or any backlog of items using the VERDICT framework. Use this skill whenever the user wants to decide what to build first, triage a backlog, sequence a roadmap, compare multiple initiatives, or score items against a consistent rubric. Also trigger when the user says…
Use when the user wants to read, catch up on, send, reply to, react to, or @mention in Microsoft Teams chat messages ("check Teams", "any messages in ", "reply in ", "message the chat", "react to that message", "@mention someone", "catch me up on Teams"). Drives the new Teams web (teams.cloud.microsoft) in Chrome via…
Decompose findings into well-scoped Linear issue drafts (one issue = one PR), preview them, and ask before filing. Never files without explicit confirmation.
Plan any multi-step project using a guided conversational interview based on the GTD Natural Planning Model. Walk the user through four phases — Purpose & Principles, Outcome Visioning, Brainstorm, Organize — plus an Execution Bridge.
Orchestrate engineering work from intent through proportionate planning, independent review, implementation, pull request creation, active review monitoring, and verified closeout. Use for /kickoff or $kickoff and for work explicitly requested as an end-to-end shipped change.
Run one Ralph-style autonomous iteration on GitHub issues / plan files inside the current Claude Code session. In-session port of ralph/afk.sh — drops Docker, claude --print, codex exec, auth tokens, and the MAXITER outer loop, so there is no per-token API cost. Args mirror the original: --issue N (repeatable), --file…
Takes a Jira ticket key and drives it end to end. Validates the ticket against the code at HEAD and against merged work, open PRs and related tickets that may have overtaken it, sizes impact and fix on a bug or security ticket, rewrites the ticket from what it found, then builds, commits, reviews and opens a draft PR.…
Autonomous GitHub Issue Fixer agent called LoachBot. Picks the single most-recently-updated GitHub issue created by and assigned to you, implements a fix in a Pull Request, then unassigns the issue. Use when the user wants to work through issues assigned to them, or asks to "run LoachBot Issues", including repeated…
Drive a task queue (loop-tasks.md) to completion in ANY repo — detect the repo's own rules, then for each task plan → /review-plan → implement → verify → /review → fix all findings → commit → push → client doc → mark done. Autonomous between tasks; pauses only for genuine product decisions.
Full development cycle - fetches ticket from work item tracker, analyzes, implements, validates, fixes build errors, and creates PR. Use when developing a ticket end-to-end.
★not rated 2 2mo agoA37 tokens
originalMIT
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: