davidondrejInstall Ask Then Build
Pick your agent. Every command is ready to paste.
npx skills add davidondrej/skills --skill ask-then-buildThe open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.
01
Install it
Run the command above, or upload the folder in Claude.
02
Ask naturally
Describe the task. Your agent loads ask-then-build when the request matches its description.
03
Name it if needed
If it does not trigger, say “use the ask-then-build skill”. In Codex, type $ask-then-build.
Turn a feature idea into a build prompt for another agent, in two phases.
Phase 1 — Questions
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.
Phase 2 — Prompt
After the last answer, deliver ONE concise paragraph prompt for another agent. It must include, in this order:
- Read-first files: the authoritative docs (AGENTS.md, requirements, ADRs).
- What to build: numbered implementation steps, concrete file-level where useful.
- How to validate: build, lint, and a manual check with real data.
- Rules: don't commit, report back with files changed.
Style
- Very concise, plain English, short sentences.
- Never bundle questions. Never write the prompt before all answers are in.
- Never put two options on one line. Always a blank line between A, B, C, D and before "My pick".
- Keep the prompt to a single paragraph — if it needs two, the scope is too big; say so.
Tips for Ask Then Build
- • Start a fresh session after installing so your agent picks up the new skill.
- • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
- • If two skills overlap, mention the one you want by name.
Questions about Ask Then Build
What does the Ask Then Build skill do?
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.
How do I install Ask Then Build?
Run "npx skills add davidondrej/skills --skill ask-then-build" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.
Does Ask Then Build work in Cursor and Codex?
Yes. Ask Then Build uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.
Is Ask Then Build free?
Ask Then Build is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.
Who made Ask Then Build?
Ask Then Build is published by davidondrej in the davidondrej/skills repository, together with 29 other skills.
