wtf is prd-writer?

vibe-coding-prd is a skill for coding agents like Claude Code and Codex that turns raw requirements into a lean Markdown product requirements document meant to be handed straight to a coding agent for implementation. It can take a rough idea, a Lark or Feishu document link, an existing PRD, competitor analysis, or scattered notes as input, and its goal is not to write persuasive business narrative but to extract what a coding agent actually needs: users, scenarios, pain points, product shape, feature scope, priorities, suggested tech stack, screen structure, detailed interactions, AI agent workflow where relevant, data and permissions, and testable acceptance criteria. The README explains the problem it addresses: many PRDs are written for human readers and are too long, too scattered, or too focused on business context, which causes coding agents to drift off track during implementation. The skill strips out marketing language and background that does not affect implementation, keeps only what is needed to build the feature, asks clarifying questions instead of guessing when requirements are vague, splits features into MVP and priority tiers, and adds agent workflow and prompt structure details for AI-driven products. It is meant for cases where someone has a rough idea, an existing PRD, or a competitor analysis that needs to become a build-ready spec for tools like Claude Code, Codex, or Cursor. It is explicitly not meant for writing marketing copy, pitch decks, or handling requirements that are already precise engineering tickets, and it is not a substitute for high-fidelity UI design. Installation is done by cloning the repository and either copying it into a local Codex skills directory or symlinking it there so future git pulls update it automatically. By default the skill outputs the PRD in Chinese unless the user asks for another language, and it needs read access to any linked Lark or Feishu document before it can extract requirements from it.