Vibecoding Product Requirements Alignment Framework

Problem

When AI starts writing code or drafting technical plans, misunderstandings may already be baked in: it may replace business language with technical language, or treat “built it” as “built the right thing.” In traditional workflows, a human states the requirement and AI implements it; the handoff becomes a design document biased toward the AI side, making early misalignment hard to detect.

How It Works

The skill splits pre-implementation work into two checks. Stage 1: Requirements Alignment asks AI to restate the request, probe key constraints, and confirm goals, scenarios, and acceptance criteria in business language. Stage 2: Critical Planning asks AI to review its own plan for hidden assumptions, missing risks, dependency gaps, and drift points. The two prompts create a loop of understanding validation and self-criticism, surfacing errors before code implementation begins.

Boundaries

It suits new product ideas, new feature requests, or major project adjustments that need requirement clarification, but it does not replace architecture design, security review, or compliance judgment. If the requirement is vague, it improves the discussion but still needs key business facts from the user; for quick demos or throwaway scripts, the extra process may be heavier than necessary.