Read-only shortlist of unassigned, ready Jira tickets your team could pick up next — active sprint first, then the next sprint and top of backlog — with flagged or blocked ones listed separately. Scoped by a workspace pickup.toml.
Read-only overview for one Jira ticket, grounded in relevant code: Problem, Solution, Steps, and Open questions. Use before implementation; recommend architect for complex or high-blast-radius work.
Opt-in conversational pairing when the user explicitly asks to pair: the agent writes authorized code in small agreed steps, discussing decisions and results throughout. Not for ordinary implementation requests.
Read-only sizing assessment of one existing bead: keep whole, clarify, or split into independently valuable outcomes, possibly under an epic. Hands any approved change to /triage; never writes.
Plan Dependabot security remediation for one repository into a few beads (a bead per urgent fix, small compatible batches, one dated follow-up), then fix one selected bead with native verification, one confirmed push and observed alert state.
Guide attended Git and Beads synchronization at a validated workspace root, with accurate previews, separate fresh approvals and explicit failure boundaries. Never sync from status or wrap-up.
Recommend GitHub reviewers from the authenticated user's previous PRs in one repository, with distinct-PR counts and evidence links. Read-only; never requests reviews.
Find recurring substantial prompts in local Pi and Claude Code history and suggest reusable prompt-template drafts; metadata-first, redacted, bounded and read-only.
★not rated 9 yesterdayA33 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: