Vibe Requirements Spec

Overview

Turn a rough coding goal into a finished Markdown requirements spec through focused questions, without inventing product behavior, scope, data rules, or success criteria. This phase writes only the spec and its declared records, then ends its own response after the spec and a short summary; implementation planning is a separate phase, which top-level orchestration may start next when the user's requested outcome needs it.

Choose the output mode first: