ksssvd/vibe-coding-prd-skill — explained in plain English
Analysis updated 2026-05-18
Turn a rough product idea into a build-ready PRD for a coding agent.
Trim a bloated original PRD down to only what a coding agent needs.
Summarize a competitor analysis into buildable MVP features.
Convert meeting notes or documents into a structured acceptance-criteria list.
| ksssvd/vibe-coding-prd-skill | 0x4d31/stinger | 5p00kyy/club-5060ti | |
|---|---|---|---|
| Stars | 23 | 23 | 23 |
| Language | — | Go | Shell |
| Setup difficulty | easy | moderate | hard |
| Complexity | 1/5 | 4/5 | 3/5 |
| Audience | pm founder | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Just a git clone into the Codex skills directory.
This project is a skill for Codex (and compatible tools like Claude Code) that turns messy product requirements into a clean, implementation-ready PRD document. The idea is that raw requirements, whether they come as a rough idea, a bloated original PRD, notes from a document tool, or a summary of a competitor's product, usually contain a lot of business context, market language, and background story that a coding agent does not need. This skill strips that out and keeps only what matters for building: features, interactions, data, and constraints. The skill is triggered by asking it, in Chinese, to write a PRD for vibe coding, or by describing that you want to turn a rough document into something a coding agent can act on. It works through a defined process: it first classifies your input as a clear requirement, a raw PRD, a competitor analysis, or a vague idea. If the requirement is unclear, it asks multiple choice questions to confirm what you actually want rather than guessing. Once the requirement is confirmed, it produces a feature list with MVP, P1, and P2 priority levels, recommends a tech stack in plain language for non-technical users, and sketches the main screens using simple ASCII diagrams. After you confirm the prototype, it fills in detailed feature designs and writes acceptance criteria that describe exactly what to click, what should appear, and how the data should change, so each item can be verified. The final output is a complete Markdown PRD with sections for requirement definition, feature list and priorities, tech stack, core screen prototypes, detailed feature design, and acceptance criteria. This document is meant to be handed directly to a coding agent such as Claude Code or Codex to start building. Installation is a simple git clone into the Codex skills folder. The project explicitly says it is not meant for writing business plans, fundraising decks, or market analysis, and it is not needed if every requirement detail is already fully decided and you just need code written.
A Codex/Claude skill that turns messy requirements or raw PRDs into a clean, build-ready PRD for coding agents.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
Verify against the repo before relying on details.