Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and handing off implementation planning to bt:plan. Use for feature ideas, problem framing, vague or ambitious requests, "what should we build" conversations, or when a user wants to think through options before deciding what to build.
Transform requirements, clarified ideas, bug reports, or improvement requests into structured implementation plans grounded in repo patterns. Use when the user wants a durable plan of work with PR-sized tasks, explicit dependencies, and a clear path to implementation.
Scaffold only. Future execution skill intended to replace or surpass the current beads-implement workflow.
File Beads or beads_rust epics/issues from a finalized plan/spec AND do the polish pass (clarity, acceptance criteria, sizing, deps). Use when asked to create Beads from a plan/spec (OpenSpec, PRD, design doc), convert an external plan into issue tracker structure, or review/refine an existing Beads set.
Implement Beads or beads_rust work items from an issue id. Use when the user runs $beads-implement <bead-id> or asks to implement a bead/epic; if it is an epic, implement all sub-tasks, committing after each one and only interrupting when blocked or a decision is needed.
Facilitate structured idea exploration and product/design specification. Use when a user wants to talk through an idea, refine it via iterative questions, and converge on a clear design/spec (and later an implementation plan), especially after inspecting the current project state.
Export a ChatGPT shared conversation to Markdown or JSON via a share URL.
Run multi-agent code review by profiling risk, selecting reviewer personas, spawning sub-agents, and merging structured findings into one severity-ordered report.