superbeads

Use when shaping a feature, component, or behavior change into an approved solution design.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when committed code is awaiting merge and its project documentation may be stale.

Use when a validated implementation graph must run without isolated subagents.

Use when implementation work has reached a terminal branch state and the user must choose merge, PR, keep, or discard

Use when an unfamiliar, stale, compacted, or unclear project session needs orientation.

Use when several memories need deduplication, consolidation, or cleanup.

Use when the user asks to establish, repair, or revise a formal product contract or explicitly requests product discovery before solution design.

Use when Beads initialization, a missing database, remote bootstrap, diverged Dolt history, or project-local Superbeads SessionStart activation is needed.

Use when code-review feedback must be evaluated before changing the implementation.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when a decision or plan needs persistent repository, external, or mixed research evidence.

Human-invoked session handoff for resuming unfinished work in a fresh context.

Use when an approved design, plan, or decision needs adversarial coverage before execution.

Use when executing a validated implementation graph with independent tasks in the current session, especially when fresh task contexts or parallel workers are requested

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

Use when implementing any feature or bugfix, before writing implementation code

Use when implementation work needs an isolated Beads-aware Git worktree.

Use when a session starts and available skills must be selected before responding.

Use before any claim that work is complete, fixed, passing, merge-ready, or accepted, including before commits, task closure, PRs, and branch completion

Use when writing or substantially revising human-facing documentation, guides, messages, or release notes.

Use when an approved product contract and solution design need a validated multi-task implementation graph.

Use when creating, editing, pruning, or behaviorally testing an agent skill.