From rails-agent-skills
Generates Markdown PRDs from feature descriptions, saves to /tasks/prd-FEATURE-SLUG.md following PRD_TEMPLATE.md. Covers goals, user stories, requirements, and metrics for Rails workflows.
npx claudepluginhub igmarin/rails-agent-skills --plugin rails-agent-skillsThis skill uses the workspace's default tool permissions.
Focus on *what* and *why*, not *how*. No code until the PRD is approved.
Generates structured Product Requirements Documents (PRDs) by gathering project context from files and commits, asking 3-5 clarifying questions with lettered options, and producing sections like user stories, functional requirements, non-goals, and success metrics.
Generates Product Requirements Documents (PRDs) for features via clarifying questions on goals, users, and scope. Structures into user stories, requirements; saves to tasks/prd-[feature].md.
Interactively generates detailed Product Requirements Documents (PRDs) for features via clarifying questions. Includes user stories, requirements, and saves to prds/[feature-name].md.
Share bugs, ideas, or general feedback.
Focus on what and why, not how. No code until the PRD is approved.
| Asset | Use |
|---|---|
| PRD_TEMPLATE.md | Mandatory Markdown structure every PRD follows |
| assets/prd_questions.md | Clarification inventory (not an obligatory 12-question form) |
| assets/examples.md | Short one-pager + full PRD example aligned to the template |
A PRD is a what/why document — never include code, pseudo-code, SQL, class names, method signatures, or migration syntax. Naming a model or controller for scope is fine; writing its methods is not.
/tasks/prd-<feature-slug>.md (lowercase, kebab-case slug — e.g. /tasks/prd-google-oauth-login.md). State the path in your response.generate-tasks against this PRD once approved.").After saving, surface the file path and request explicit approval before any implementation or task generation.