5 workflows

runcastle

An Opus planner triages your open `bug`-labelled GitHub issues into independent fixes, then a swarm of Sonnet fixers fans out — one per issue, each on its own branch — to reproduce, root-cause, patch, and test the bug in parallel.

runcastle

A single Claude Code agent reads raw meeting notes and turns every actionable item into a clean, ready-to-file issue draft — one markdown file per action with title, context, acceptance criteria, and a suggested owner and label — plus an INDEX.md summary table.

runcastle

Reads a links.md list of URLs, fetches each one inside the sandbox, and has a Claude Code agent write a ready-to-send newsletter digest — a tight 2–3 sentence summary of every link, why it matters to your readers, and the source link, all assembled into a single markdown issue.

runcastle

A single Claude Code agent reads a metrics.csv, computes week-over-week deltas, and writes an executive narrative — what moved, why it likely moved, what to watch, and one recommended action — alongside a compact metrics table, to reports/weekly.md.

runcastle

A single Claude Code agent turns an incident timeline and the last week of commit history into a blameless postmortem — summary, impact, timeline, root causes, contributing factors, what went well, and action items with owners and due dates — written to postmortem/POSTMORTEM.md.