Swarm planning session with PM, UX, and Engineering agents who debate an idea, ask clarifying questions, and produce a detailed spec written to plans/$plan-name.md.
Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.
Record a visual demonstration of the key feature of this PR using screenshots and add it as a new comment to the PR.
Add one or more AI models to the language model constants file, researching specs from official docs.
Review the current session for errors, issues, snags, and hard-won knowledge, then update the rules/ files (or AGENTS.md if no suitable rule file exists) with actionable learnings.
Turn customer feedback (usually an email) into discrete GitHub issues. Checks for duplicates, proposes new issues for approval, creates them, and drafts a reply email.
Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.
Identify and fix flaky E2E tests by running them repeatedly and investigating failures.
Debug a specific session by inspecting its full event chain (PreToolUse, PostToolUse, Stop, SubagentStop, Compaction, APIError, TurnDuration, Notification events), agent hierarchy…
Promote the latest pre-release to a stable release by creating a release branch, bumping the version, and pushing.
Multi-agent code review system that spawns three independent Claude sub-agents to review PR diffs. Each agent receives files in different randomized order to reduce ordering bias.
Root-cause flaky or failing E2E tests from a specific CI run by downloading and analyzing the Playwright HTML report (traces, screenshots, errors).
Automatically gather flaky E2E tests from recent CI runs on the main branch and from recent PRs by wwwillchen/keppo-bot/dyad-assistant, then deflake them.
Team-based PR review using Claude Code swarm. Spawns three specialized teammates (correctness expert, code health expert, UX wizard) who review the PR diff, discuss findings with…
Check GitHub Actions workflow runs from the past day, identify severe or consistent failures, and file an issue if actionable problems are found.
Map a minified error stack trace from a production Dyad build back to original source locations using source maps.
Rebase the current branch on the latest upstream changes, resolve conflicts, and push.