agent-workflow-beads

Remove a sibling git worktree created by `executor-task-worktree`, `executor-epic-task-worktree`, `executor-epic-sequential-worktree`, or `create-new-worktree` once follow-up work (review comments, screenshots, CI fixes) is done. Lists existing worktrees, confirms which to remove, verifies the branch is safe to drop (PR merged or user-approved), removes the worktree, prunes stale entries, and optionally deletes the local branch.

Run every ready child bead of one epic end-to-end, sequentially, on a single epic branch (epic/<epic-bead-id>). Each bead executes in a fresh headless `claude -p` session so context never carries between tasks; a failed bead is marked blocked and skipped (along with its dependents) and the run continues; finishes with one PR from the epic branch to the default branch. Use when the user wants to deliver a whole epic unattended as one branch and one PR instead of running one bead at a time.

Use when you want to deliver a whole epic unattended as ONE branch and ONE PR WITHOUT disturbing in-flight work in the main checkout. Runs every ready child bead of one epic sequentially in a fresh sibling git worktree checked out on the epic branch (epic/<epic-bead-id>) so the main working tree is never touched — each bead executes in its own fresh headless `claude -p` session (clean context per task), committing directly onto the single epic branch; a failed bead is marked blocked and skipped (along with its dependents) and the run continues; finishes with one PR from the epic branch to the default branch and leaves the worktree in place for follow-up (review comments, CI fixes). Use the `cleanup-worktree` skill to remove the worktree once the PR has landed.

Run a full executor cycle for one bead on a fresh feature branch off its parent epic branch (epic/<epic-bead-id>): stash any in-flight work, switch to the epic branch, pull, create feat/<bead-id>-<short-slug>, execute the bead end-to-end, then push and open a PR targeting the epic branch. Use when the user wants a single bead delivered as its own PR into an in-progress epic branch instead of main.

Run a full executor cycle for one bead in a fresh git worktree off its parent epic branch (epic/<epic-bead-id>): leaves the main working tree completely untouched, creates a sibling worktree at ../<repo>-feat-<bead-id>, executes the bead end-to-end, pushes, opens a PR targeting the epic branch, and leaves the worktree in place for follow-up work (review comments, screenshots, CI fixes). Use when an epic has its own integration branch and the main tree has active work that must not be disturbed. Use the `cleanup-worktree` skill to remove the worktree once follow-up work is done.

Delete local git branches whose upstream was removed from origin, and tear down any sibling git worktree still attached to them. Use when the user asks to clean up stale, pruned, merged, or deleted remote branches locally — including the worktrees the executor-*-worktree / create-new-worktree flows leave behind.

Use when the user wants to rebase the current branch onto its up-to-date base and force-push with lease — e.g. "rebase this branch", "rebase and push", "bring my branch up to date with the epic", "bring the epic branch up to date with main". Works on a feature branch (rebased onto its parent epic branch epic/<epic-bead-id> or the default branch main/master) and on an epic branch itself (rebased onto the default branch). Detects the base, rebases onto the matching origin ref, resolves conflicts, runs verification-before-completion, then pushes with --force-with-lease. Maintenance op; refuses to run on the default branch, and stops to confirm before rebasing an epic branch that still has open child PRs targeting it.

Use when the user wants to spin up a fresh sibling git worktree from a branch name or a bead id/name, off the origin default branch — seed its `.env*`, optionally copy other git-ignored working files, install dependencies, and ensure Beads is operational inside it — then stop and hand off to an executor. Setup only: never claims the bead, plans, or implements. Use the `cleanup-worktree` skill to remove the worktree afterward.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements. Dispatches the repo-local code-reviewer subagent.

Audit ready and blocked beads for drift against the current CLAUDE.md / AGENTS.md rules (folder structure, naming conventions, project rules). Use after editing CLAUDE.md or AGENTS.md to find beads whose Read/Files/Inputs/Verify sections still reference old conventions, paths, or rules.

Use at the start of an executor session to find and claim a ready bead. Do not invoke in planner sessions.

Use after implementation and verification are complete to close the bead, create follow-up beads, and commit the updated `.beads/` state. This is the final step of a manual executor session.

Break a discussed or settled problem into Beads epics and tasks with clear dependencies and validation work. Use when the user wants to turn a problem statement, planning discussion, or settled execution plan into a Beads structure instead of ad-hoc TODOs.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.

Re-execute one bead on the current feature branch in the current main worktree, after its requirements were updated and its PR is already open. Requires bead_id. Does NOT create a branch, switch to main, or open a new PR — just re-claims, re-plans, re-implements, verifies, re-reviews, closes the bead, then pushes into the existing PR with a fixup summary comment.

Run a full executor cycle for one bead on a fresh feature branch off main: stash any in-flight work, switch to main, pull, create feat/<bead-id>-<short-slug>, execute the bead end-to-end, then push and open a PR. Use when the user wants a single bead delivered as its own PR.

Run a full executor cycle for one bead in a fresh git worktree off main: leaves the main working tree completely untouched, creates a sibling worktree at ../<repo>-feat-<bead-id>-<short-slug>, executes the bead end-to-end, pushes, opens a PR, and leaves the worktree in place for follow-up work (review comments, screenshots, CI fixes). Use when the main tree has active work that must not be disturbed. Use the `cleanup-worktree` skill to remove the worktree once follow-up work is done.

Use after all work on a feature branch is complete and verified. Pushes the branch and creates a PR targeting main.

Run a planner-only Beads session: brainstorm, produce or confirm an execution plan, brief the user once for bead creation, then create beads and stop. Use when the user wants to turn a current problem or topic into Beads without implementing.

Planner-only research step for resolving factual unknowns after brainstorming and before Beads creation. Use only when unresolved technical or domain uncertainty would materially weaken the plan.

Prepare a USB-connected Android phone so the user (or follow-up tools) can drive Chrome on it via the chrome-devtools-android MCP server. Verifies adb, ensures Chrome DevTools is reachable, registers/forwards the MCP endpoint, and — if a localhost URL is given — sets up adb reverse for the dev server. Performs no navigation, no screenshot, no audits, and no cleanup.

Run a full-repo audit covering naming conventions, folder structure, tech stack consistency, and a light architectural pass. Use when the user asks to audit, review consistency, or get a project health check.

Use when asked to check, screenshot, or fix how a web page renders across screen sizes - loads the page at 320/375/425/768/1024/1280px via the Chrome DevTools MCP, screenshots each, and fixes any horizontal overflow or layout break before reporting

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Validate a planned epic before autonomous execution. Use after beads-planner to check dependency quality, bead size, fresh-session-safe bead contracts, verification instructions, and parallel-safety notes.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code. This is an executor skill - use only when a bead has been claimed and you are in an executor session, NOT in a planner session.

Use to iteratively address unresolved review comments on the current PR. Fetches unresolved inline threads AND non-inline conversation comments, dispatches the pr-comment-fixer subagent to apply fixes, then verifies, commits, pushes, and posts replies. The reviewer resolves threads on their side; rerun the skill when new comments arrive.

Use after implementing a web UI feature to capture browser screenshots at all Tailwind breakpoints and attach them to the open PR.

Use after implementing changes to run the exact verification commands from the current execution plan. This stage-1 version is intentionally generic and should be specialized per repo once the runtime workflow is clear.

Use after authoring or editing a SKILL.md in this template repo, before committing or shipping it downstream - dispatches a fresh subagent to test whether the skill holds up under realistic pressure. Template-repo-only; not shipped downstream.