Individual skill
ask-then-build
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.
skills/thinking-and-docs/ask-then-build/SKILL.md
Source commit 8aa01cf45110ae378bdf5c319cd41ac8fdbdf448
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 4,282
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,239 bytes
Read excerpt
Turn a feature idea into a build prompt for another agent, in two phases.
## Phase 1 — Questions
1. 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.
2. 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?**