Generate a structured PRD Markdown document from a feature description.
npx skills add https://github.com/igmarin/rails-agent-skills --skill create-prd-igmarin
Please help me install this Agent Skill. Skill: create-prd Source: https://github.com/igmarin/rails-agent-skills/tree/main/create-prd Command: npx skills add https://github.com/igmarin/rails-agent-skills --skill create-prd-igmarin
Creating high-quality PRDs is time-consuming and error-prone without a clear, structured template. This Skill automates the generation of a Markdown-form PRD from a feature description, ensuring consistency and completeness across teams.
Describe a feature and any constraints; the tool will generate prd-[feature-name].md in /tasks and present a ready-to-review document.
High-intent search queries and answers about installing and using this skill.
To generate a structured PRD for a Rails feature, describe your feature and constraints. The tool outputs a Markdown document capturing goals, user stories, functional requirements, non-goals, and discovery prompts, saving it directly to your /tasks directory.
A PRD for Rails development should include goals, user stories, functional requirements, non-goals, and discovery prompts. This tool automatically structures these sections into a Markdown file to ensure consistency and completeness for engineering handoff.
You can turn feature ideas into actionable tasks by generating a PRD Markdown file, then requesting optional task-generation guidance. The tool provides handoff support via generate-tasks or jira-ticket-planning to map requirements into implementation steps.
This PRD generator targets Rails-oriented workflows specifically. While the structured Markdown output containing goals and user stories is broadly applicable, its workflow optimizations and task handoff guidance are tailored for Rails development teams.
Generated PRD documents are saved as Markdown files in the /tasks directory. The file is automatically named using the prd-[feature-name].md format, making it easy to locate for team review and approval.
The best way to create consistent product documentation is using a structured template that enforces sections like goals, user stories, and functional requirements. This tool automates that structure into a standard Markdown format, reducing manual errors and saving time.
deloreyjGenerate structured Markdown PRDs with problem, scope, constraints, and acceptance criteria.
ramybarsoumConvert approved Feature Doc Section 5 use cases into engineering tickets for Linear, Jira, or text.
pwnk77Generate structured PRDs and convert them into prioritized tasks.
KeyValueSoftwareSystemsSynthesize product requirement documents from unstructured inputs into prd.md.
