Turn a feature or refactoring idea into a concise implementation prompt for another agent. It asks focused questions one at a time, records decisions, and includes development steps, validation, and working rules.
Clarify a feature, change, or refactor through questions, then write a build prompt for another agent. Use for /ask-then-build or requests to ask questions before producing an implementation prompt.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Turn a feature idea into a build prompt for another agent, in two phases.
Identify the 3-6 most non-obvious open questions about the feature or change: edge cases, where it lives in the UI, failure behavior, scope boundaries, how it interacts with existing rules.
Ask them ONE at a time. For each: the question, top options A-D, your preferred pick with a one-line reason. Then stop and wait. Use this exact layout. Put a blank line between EVERY block. Markdown renderers (bb included) collapse single newlines into one paragraph, so options written back-to-back render as one run-on blob.
Question title?
One line of context, if needed.
A. First option.
B. Second option.
C. Third option.
D. Fourth option.
My pick: A. One-line reason.
Never number questions as "1 of N" unless you truly know N. If the count is open, keep it open and keep asking until you have the context you need.
When the user answers, record the decision immediately — update the repo's docs (product requirements, ADR, or README) if the project has them.
If the user overrides an earlier documented decision, update the docs right away and say what was superseded.
After the last answer, deliver ONE concise paragraph prompt for another agent. It must include, in this order:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Work through sixteen open questions in four rounds to clarify major product decisions, risky changes, or large refactors. The agent adapts later questions to earlier answers, then turns your decisions into a step-by-step implementation plan.
Document approved decisions as concise ADRs, or architecture decision records. It preserves the user's meaning and conditions, removes conversational filler, follows the project's numbering, and presents the saved record for review.
Keep a Mac awake for a chosen duration or while a specified process runs. The skill uses built-in macOS tools to manage one session, verify that sleep prevention is active, and control whether the display stays on.
Inspect and manage BB threads, environments, projects, and plugins through its command line interface. The skill guides agents to identify the correct targets, apply changes, and verify the resulting state.
Create, install, and debug TypeScript plugins that extend bb with custom pages, sidebar panels, CLI commands, agent tools, themes, and other features. The skill also guides development reloads, log checks, and verification of installed plugins.
Identify one to three important decisions before starting a build. Based on the user's idea, this skill presents concise options and an initial recommendation for each, then waits for answers before work proceeds.