suqiyue2001/vibe-coding-prd — explained in plain English
Analysis updated 2026-05-18
Turn a messy product idea into a structured PRD ready for a coding agent.
Distill an existing PRD down to the parts relevant for implementation.
Convert competitor analysis notes into a list of candidate features.
Pull a Feishu or Lark document into a coding-ready requirements draft.
| suqiyue2001/vibe-coding-prd | mfolejewski/pcie_mux | stealthyboy93/bibata-catppuccin-cursor | |
|---|---|---|---|
| Stars | 16 | 14 | 19 |
| Language | None | None | None |
| Setup difficulty | easy | hard | easy |
| Complexity | 1/5 | 5/5 | 1/5 |
| Audience | vibe coder | developer | general |
Figures from each repo's GitHub metadata at analysis time.
vibe-coding-prd is a Codex Skill that turns rough ideas, existing PRDs, competitor notes, or Feishu and Lark documents into a compact, implementation ready product requirements document that a coding agent can build directly from. It is meant to sit between a person's messy description of what they want and the structured document an AI coding assistant needs to start working. The skill handles several kinds of input differently. A clear requirement gets turned into a definition covering the user, the scenario, the pain point, the product form, and the minimum viable scope. A raw existing PRD gets stripped down to the parts that matter for coding, removing business narration. Competitor analysis gets converted into a product direction with candidate features and differentiators. A Feishu or Lark document link gets fetched through a tool called lark-doc, then distilled the same way. When the idea itself is unclear, the skill asks multiple choice clarifying questions before drafting anything rather than guessing. The output follows a fixed structure: requirement definition, minimum viable product scope and priority, a recommended technology stack, a prototype wireframe description, detailed functional design for each module, concrete acceptance criteria, what is explicitly out of scope, and any open questions. The design principles behind the skill emphasize never guessing when intent is unclear, favoring concrete things like screens, states, flows, tools, prompts, and APIs over business value prose, keeping the document lean, separating must build features from later improvements, and making sure every feature has a testable, observable acceptance criterion. To use it, you clone or copy the repository into your Codex skills directory, then start a new Codex thread and invoke it by name along with your requirements, in either English or Chinese. The repository itself is intentionally small, with the core workflow defined in a SKILL.md file and a small YAML file providing metadata for the Codex interface. The README does not state a license for the project.
A Codex Skill that turns rough ideas, PRDs, or competitor notes into a lean, coding-agent-ready product requirements document.
Mainly None. The stack also includes Codex, Markdown, YAML.
Not stated in the README.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly vibe coder.
This repo across BitVibe Labs
Verify against the repo before relying on details.