10 workflows

runcastle

A single Claude Code agent that finds the least-tested modules in your repo, writes focused unit tests for them one module at a time, and verifies the suite stays green after every batch — stopping once it hits your coverage target.

runcastle

Fans out an analyst agent per competitor to fetch and dissect each rival's site — pricing, positioning, messaging, gaps — then a strategist synthesizes the teardowns into a single positioning brief with sharp, defensible angles for your product.

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

Reads a sources.md list of papers, fetches each one, and builds a structured literature review — per-source summary of question, method, finding, and limitation — then synthesizes the themes, disagreements, and open gaps across the whole set.

runcastle

A single Claude Code agent reads your product and segment notes, then produces a defensible TAM/SAM/SOM estimate using both top-down and bottom-up methods — every assumption stated, a sensitivity table, and honest caveats — written to research/market-sizing.md.

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

Turn a single topic into a publish-ready blog post through three sequential Claude Code passes on one warm branch: an Opus strategist outlines the angle and keywords, a Sonnet writer drafts the full post, and an Opus editor tightens the prose and optimises it for search.

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 reads your repository — a shell-expanded file map seeds it, and it can install and run the project — then writes and incrementally commits a real `docs/` set: a getting-started guide, an architecture overview, and per-module reference pages.

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.