Vibe Requirements Spec

Overview

Turn rough coding intent into a Markdown requirements specification artifact without inventing product behavior, scope, data rules, or success criteria.

The spec is input to a later implementation-planning phase. Requirements lifecycle state is workflow evidence, not spec content: record requirements- finished or next-phase handoff evidence in the chat summary or active routing state when available, but do not write approval, completion, readiness, or handoff state anywhere in the spec artifact, including metadata, risks, or acceptance criteria. Open requirement decisions and unknowns stay in their ordinary spec sections without interpreting them as lifecycle status. This skill stops after the spec artifact and concise summary. Do not require or name a specific downstream planning workflow unless the user named one as context. In a response-only lifecycle classification, do not stop at saying that an ambiguous reply or prior summary is insufficient. State that the current-spec completion audit must be run or rerun before finish or handoff can be accepted.