speckit-adlc-levelup-clarify

Clarifying CDRs involves applying a structured workflow to generate targeted questions, consult team directives, and capture decisions with evidence to reach accepted or deferred outcomes. This resolves ambiguities by enforcing traceable status changes for each interaction.

Decision traceability in the spec-kit workflow is tracked by capturing context, decision, evidence, and status changes in structured logs. This ensures every clarification interaction is recorded to validate CDRs against team directives and accelerate implementation.

Validating proposed CDRs against team directives requires consulting the directives during the clarification phase to avoid misalignment. The process generates targeted questions to fill gaps in context and evidence, ensuring decisions align with team standards before approval.

Yes, the workflow applies to all CDRs listed in the draft markdown file located in the repository's specify directory. It processes pending CDRs sequentially through interactive clarification sessions to track statuses and decisions.

Filling gaps for discovered CDRs is best handled by generating targeted questions during the clarification phase. This structured approach identifies missing context and evidence, guiding the CDR toward an accepted or deferred status with traceable logs.

Deferring CDRs instead of accepting them occurs when targeted questions reveal unresolved ambiguities or missing evidence. The workflow enforces capturing the deferral context and status change in traceable logs to revisit the decision later.