context-to-prd
Skill12 starsChanged 32 days agoLicence not identifiedView on GitHub
把已经聊透的需求上下文直接落成 PRD，不做采访。适用于你已经跟 AI 把问题、边界、方案讨论清楚，只差成文的场景；需求还停在口头、边界没问清时改用 requirement-clarify，要复用已有产品体验基线或做增量 PRD 时用 prd-write。产物与 prd-write 完全同构，落在 docs/prd/<feature-name>/prd.md。
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- acceptance-checklistSkill
- design-spec-prototyperSkill
- grill-with-prdSkill
- pm-frontend-prototypeSkill
- prd-writeSkill
- product-experience-foundationSkill
- product-prd-extractSkill
- prototype-htmlSkill
- prototype-to-productSkill
- requirement-clarifySkill
- web-design-extractorSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.