6 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 mixed-provider copy pipeline: a Claude Code writer turns your product brief into full AIDA-structured landing page copy, then a Codex editor cuts fluff, makes claims concrete, and tightens headlines on the same warm branch, looping until it ships.

runcastle

A Claude Code writer drafts an X/Twitter launch thread from your product brief, then a Codex critic tears it apart post-by-post — hook, clarity, specificity, CTA — rewriting the weak posts on the same warm branch until the thread is ready to ship.

runcastle

A Claude Code agent performs a refactor, a hard `npm test` gate proves nothing broke, then a Codex reviewer adversarially audits the change on the same warm branch — hunting regressions, weak tests, and shortcuts — fixing and looping until it approves.

runcastle

Fetches a single target page and audits its on-page SEO — title, meta, headings, canonical, Open Graph, structured data, alt text, internal links, word count — then writes a prioritized, fix-by-fix action list you can hand to a developer.

runcastle

Fans out a searcher per sub-question to fetch and note public web sources, then an Opus synthesizer writes a fully cited report, then a Codex fact-checker adversarially verifies every claim against the notes and loops until the report holds up.