ask-then-build git:20260902.9dc174bA

Immutable. This exact content never changes and is served at /api/v1/blob/710ed564a5d9330d.

---
name: ask-then-build
description: 'Scope a feature, change, or refactor by asking David 3-6 pointed questions ONE at a time (options A-D, state a preference, wait), record every answer, then deliver ONE concise paragraph prompt that another agent can implement from. Use when David says "ask-then-build", "ask me questions then give me a prompt", or wants a spec turned into a build prompt for another agent. Differentiator: question-then-prompt loop; next-decision only drills decisions, brain-to-docs extracts vision into docs.'
---

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?**

   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.
3. When David answers, record the decision immediately — update the repo's
   docs (product requirements, ADR, or README) if the project has them.
4. If David 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:

1. Read-first files: the authoritative docs (AGENTS.md, requirements, ADRs).
2. What to build: numbered implementation steps, concrete file-level where
   useful.
3. How to validate: build, lint, and a manual check with real data.
4. 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.