Setting the file. One moment.
Subchapter 28.3
references/phases/clarify/clarify.mdMarkdown4 KBView on GitHub
Phase 2 of 6 — Ask adaptive questions before design begins, then interpret answers into ready-to-apply design constraints.
HARD GATE — Clarify before Design: Do not load (or any later phase) until this phase finishes records as . Writing without updating phase status is a protocol violation. If the user asks to skip questions, use documented defaults and still complete this phase (including phase status).
references/phases/design/design.md$MIGRATION_DIR/.phase-status.jsonphases.clarify"completed"preferences.jsonThe output — preferences.json — is consumed directly by Design and Estimate without any further interpretation.
Questions are organized into three batches (≤7 per batch) presented sequentially. A standalone fast-path mode exists for simple stacks (< 5 apps, no Private Spaces, no Kafka).
Load references/phases/clarify/clarify-interview.md and follow it. It handles the
prior-run check, determines fast-path eligibility, selects the active question set,
and presents the questions in progressive batches — interpreting each answer. It
contains the full Question Catalog and Defaults Table.
Load references/phases/clarify/clarify-assemble.md (the phase’s assembler) and
follow it to assemble the final preferences.json, run the validation checklist +
completion handoff gate, and update .phase-status.json. It owns the artifact-level
contract for this phase.
This phase covers requirements gathering ONLY.
FORBIDDEN — Do NOT include ANY of:
Your ONLY job: Understand what the user needs. Nothing else.