zekovicjasmina660-cloud/vibe-coding-prd-skill — explained in plain English
Analysis updated 2026-05-18
Turn a vague product idea into a structured PRD by answering clarifying multiple choice questions.
Strip business jargon out of an existing PRD so a coding agent can act on it directly.
Convert a competitor analysis document into candidate features and a differentiation plan.
Rewrite a Lark or Feishu requirements document into a PRD formatted for Claude Code or Codex.
| zekovicjasmina660-cloud/vibe-coding-prd-skill | 1296018244/grok-manager | 787a68/hubproxy | |
|---|---|---|---|
| Stars | 16 | 16 | 16 |
| Language | — | Go | Go |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 1/5 | 3/5 | 3/5 |
| Audience | pm founder | ops devops | ops devops |
Figures from each repo's GitHub metadata at analysis time.
This project is a "skill" for AI coding agents like Codex and Claude Code, designed to turn messy product requirements into a clean, ready-to-use PRD (product requirements document). A PRD is a written plan that describes what a piece of software should do before anyone starts building it. The skill accepts several kinds of input: a clear set of requirements someone already wrote out, a raw original PRD full of business language, a linked document from Lark or Feishu (workplace collaboration tools popular in China), a writeup comparing competing products, or even just a vague idea that has not been thought through yet. Depending on what it receives, the skill either breaks the requirement into feature modules and priorities, strips out marketing language from an existing PRD, reads and rewrites a linked document, turns competitor analysis into candidate features and questions, or asks the user multiple choice questions to clarify a fuzzy idea. Once the input is understood, the skill walks through a set flow: confirming the minimum viable scope and priority order, suggesting a technology stack, sketching a rough prototype structure, listing detailed feature modules, and writing testable acceptance criteria. The final output is a structured Markdown document with sections covering the requirement definition, MVP scope, recommended tech stack, a basic prototype layout, detailed feature design, acceptance criteria, and instructions aimed at a coding agent. The design principles behind it include never guessing at unclear requirements without asking, avoiding business jargon that does not help someone build the software, prioritizing a working minimum version over a fully-featured one, and writing acceptance criteria that can actually be checked rather than vague statements like good experience. Installing it means copying the repository into a Codex skills folder. Someone would use this if they have a rough idea, an old-style business PRD, or a competitor analysis and want it converted into something a coding agent like Claude Code can act on directly, without extra back and forth.
A skill that converts raw requirements, old PRDs, or vague ideas into a clean Markdown PRD that a coding agent like Claude Code or Codex can act on directly.
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.