lxj960202-jerry/write-vibe-coding-prd — explained in plain English
Analysis updated 2026-05-18
Turn a one-sentence product idea into a confirmed requirement definition through guided multiple-choice questions.
Strip business narrative out of an engineer-facing draft PRD while keeping the actionable details.
Sort a competitor analysis into features to adopt, adapt, or explicitly skip.
Produce a full PRD with MVP scope, tech approach, prototype outline, and per-feature acceptance criteria.
| lxj960202-jerry/write-vibe-coding-prd | 0xdea/ttyinject-rs | 0xhossam/uncanny | |
|---|---|---|---|
| Stars | 12 | 12 | 12 |
| Language | — | Rust | C |
| Setup difficulty | easy | moderate | hard |
| Complexity | 2/5 | 4/5 | 5/5 |
| Audience | pm founder | researcher | researcher |
Figures from each repo's GitHub metadata at analysis time.
Installed by cloning the repo and copying its skill folder into a local Codex skills directory.
Write Vibe Coding PRD is a Skill for Codex and Claude Code, meaning it is a defined capability those coding AI agents can use, that takes scattered requirements, rough draft PRDs, competitor analysis, or Lark documents and turns them into a short product requirements document the AI agent can actually understand, build from, and check its own work against. The problem it addresses is that a PRD written for a human team is often not clear enough for a coding agent: feature boundaries stay vague, decisions never get confirmed, and acceptance criteria are not concrete enough to verify. The Skill works by first clarifying what is unclear, then designing the feature set, and finally producing the coded-ready document. A single unclear sentence gets turned into a confirmed requirement definition through multiple choice questions, an engineer-facing draft PRD gets stripped of business narrative while keeping behavior, rules, data, and edge cases, and a competitor analysis gets sorted into what to adopt, what to adapt, and what to explicitly skip. When information is missing, the Skill avoids asking open-ended questions like please describe in detail, and instead offers multiple-choice options relevant to the context, confirming only one to three key questions at a time while tracking what is confirmed, pending, explicitly out of scope, and deferred to later. The final PRD it produces covers the requirement definition with users, scenarios, and pain points, a feature list with an MVP scope and priorities, a technical approach explained per feature, a low-fidelity prototype outline of pages and flows, and for AI products, the agent workflows, prompts, and tools involved, plus acceptance criteria with clear pass and fail conditions. The README lists quality guardrails: it will not present a recommendation as a confirmed requirement, will not use unverifiable phrases like good experience, will not silently copy competitor features, and will not invent data, permissions, or constraints the user never provided. Installation is done by cloning the repository and copying its skill folder into a Codex skills directory.
A Codex and Claude Code Skill that turns rough requirements, draft PRDs, or competitor analysis into a confirmed, coding-agent-ready Markdown PRD.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.