propose_design_questions
Generates clarifying questions and draft requirements to refine a project brief, ensuring clear requirements before code review or design work.
Instructions
Draft clarifying questions and candidate requirements to sharpen a build/improvement brief.
The first step of the Architect pipeline (the *grill*). Mirrors propose_research_questions
but for software projects: offloads brainstorming the requirements interview to a cheap
agy model. Returns clarifying questions (each with answer options) the orchestrator should
put to the user, plus a draft set of requirements. The orchestrator asks the user, refines,
and writes requirements.md before spending quota on a code review or design doc.
Returns JSON: {"clarifying_questions": [{"question", "why", "options": [...]}],
"draft_requirements": [...]}. Falls back to raw text if the model returns non-JSON.
Args:
goal: The project goal — what to build or improve.
repo_path: Optional path to an existing codebase being improved (gives the model context).
context: Optional extra context (users, constraints, deadline, what already exists).
tier: Model tier for the brainstorm (default 'flash' — this is a cheap task).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal | Yes | ||
| tier | No | flash | |
| context | No | ||
| repo_path | No |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |