beads-superpowers

Skills

21 in the Claude listing

• brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
• Dispatching parallel agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
• Document releaseUse when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ens
• Executing plansUse when you have a written implementation plan to execute in a separate session with review checkpoints
• Finishing a development branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
• Getting up to speedOrients on an unfamiliar or stale codebase at the start of a session, after compaction, or whenever the project state is unclear.
• Memory curatorUse at session-close when a session captured several new memories, or on-demand, to consolidate, deduplicate, prune, and structure the beads memory store.
• Project initUse when beads/Dolt database initialization fails, when bd commands return errors about missing databases, when setting up beads in a new project, or when recovering from diverged Dolt history.
• Receiving code reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative
• Requesting code reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements
• Research driven developmentUse when the user asks a question about a topic, requests research, or when understanding something is needed before planning.
• Session handoffA human-invoked utility that writes a grounded session-handoff document (plus a continuation pointer memory) so a fresh agent can resume in-progress work.
• Stress testUse when a design, plan, or decision needs adversarial scrutiny before proceeding.
• Subagent driven developmentUse when executing implementation plans with independent tasks in the current session
• Systematic debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
• Test driven developmentUse when implementing any feature or bugfix, before writing implementation code
• Using git worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verificat
• Using superpowersUse when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
• Verification before completionUse 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
• Write documentationUse when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read.
• Writing plansUse when you have a spec or requirements for a multi-step task, before touching code