blockmatic Purpose and inputs
Use when missing requirements prevent a sound plan. Read the task, relevant docs and implementation before asking what the repository already answers.
Steps
- Separate known facts, reversible assumptions, and decisions that belong to the user.
- Ask only questions whose answers change scope, architecture, acceptance criteria, or a consequential boundary. Offer concise choices when useful; avoid a fixed interview quota.
- Incorporate answers into the existing task or plan. Continue independent work while awaiting an answer where the harness supports it.
Verification and handoff
- The remaining questions affect a concrete decision.
- Accepted answers and assumptions are reflected in the next step.
- An already-authorized implementation is not delayed by a second generic confirmation.
Continue the requested planning or implementation once its required inputs are available.