wtf is vibe-coding-prd-skill?

Vibe Coding PRD Skill is a Codex skill that takes messy requirement material such as raw requirements, existing product documents, meeting style notes, or competitor analysis, and turns it into a clean product requirements document that a coding agent like Claude Code or Codex can act on directly. The problem it addresses is that most source material is not written with a coding agent in mind: it might be full of business language, read like meeting minutes, only cover what competitors are doing, or mix a lot of background story in with the actual feature requests. The skill first figures out what kind of material it has been given, then works through a series of steps: pulling out the details a coding agent actually needs, confirming what the requirement really is and what belongs in a first version, designing the feature modules, suggesting a technology stack, sketching a framework level prototype, and writing specific acceptance criteria for each feature. The final Markdown document covers a task summary, the distilled input, a clear requirement definition, the scope of the first version, suggested frontend, backend, database, and AI or agent components, a rough prototype layout, detailed module design, and testable acceptance criteria for every feature. You use it by copying its folder into your Codex skills directory, then simply asking, in a normal sentence, to turn a requirement or existing document into a PRD suitable for a coding agent. Its stated design principles are to clarify before designing, never guess at the core requirement on the user's behalf, use multiple choice questions to pin down anything vague, avoid business jargon since the output is meant for a coding agent, and require every feature to carry a clear, testable acceptance criterion. The README notes plainly that no license has been specified yet, and asks anyone using it publicly to add one first.