Vibe Requirements Spec

Overview

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

This skill is a requirements-spec drafting workflow while active. The only allowed write is creating or updating the current requirements spec artifact. Do not create implementation plans, implementation task entries, code changes, tests, verification command lists, commits, release work, changelog entries, or unrelated files while using this skill.

The spec is input to a later implementation-planning phase. Approval is workflow evidence, not spec content: record it in the chat summary or active routing state when available, but do not write approval-status fields into the spec artifact. 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.