Turn a vague product idea into a structured PRD a coding agent can act on.
Convert an existing business-focused PRD into a lean, jargon-free build spec.
Rewrite a competitor analysis into concrete feature requirements.
Get guided follow-up questions when your requirements are still unclear.
| yy-march/yuyu | 100/stock-analysis-markov | 100/tab-organizer | |
|---|---|---|---|
| Stars | 11 | 11 | 11 |
| Language | — | Java | JavaScript |
| Last pushed | — | 2016-12-25 | 2021-03-01 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | easy | easy | easy |
| Complexity | 2/5 | 3/5 | 1/5 |
| Audience | pm founder | researcher | general |
Figures from each repo's GitHub metadata at analysis time.
Requires the Codex coding assistant already installed, copy the folder into ~/.codex/skills.
This project, also called Vibe Coding PRD Skill, is another Codex Skill, meaning it plugs a new ability into the Codex coding assistant. Its purpose is to take messy, unstructured product requirements and turn them into a clean, short PRD document that a coding agent like Claude Code or Codex can act on directly. The kind of input it accepts is broad: a vague idea, a raw product requirements document, a competitor analysis, meeting notes, or a linked document from a workspace tool. It converts whatever it is given into the specific things a coding agent needs to start building, including who the product is for, what problem it solves, the scope of features split into modules with MVP versus later priorities, suggested technology choices sized for a non-technical builder, a rough text description of the core screens and user actions, more detailed design covering agent workflows, prompts, and tools for AI products or feature specifics for traditional products, and clear pass or fail acceptance criteria for each feature. If the input requirements are unclear, the skill is designed to ask the user simple multiple choice style questions about the target user, scenario, pain point, and product shape before writing anything, rather than guessing. It also strips out business strategy language, reporting tone, and internal jargon so the final document stays short and readable by an agent. The finished PRD follows a fixed outline: requirement definition, product goals, feature scope and priority, suggested tech stack, prototype layout, detailed feature design, acceptance criteria, and open questions. Installation is copying the skill folder into a local Codex skills directory and restarting Codex. It is licensed under MIT.
A Codex skill that turns messy requirements or PRDs into a short, build-ready PRD for coding agents.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
double-check against the repo, no cap.