PRD: [Feature Name]

Introduction

[One paragraph: what this feature is and what problem it solves.]

Goals

• [Measurable objective 1]
• [Measurable objective 2]

User Stories

• As a [role], I want [action] so that [benefit].
• As a [role], I want [action] so that [benefit].

Functional Requirements

1. The system must [behavior]. [Testable condition.]
2. The system must [behavior]. [Testable condition.]

Non-Functional Requirements

• Performance, security, accessibility, reliability, or scalability constraints relevant to the feature (testable where possible).

Non-Goals

• [Explicitly out of scope for this version.]
• [Explicitly out of scope for this version.]

Design Considerations

[UI/UX notes, mockup links, component references, or pending design decisions.]

Technical Considerations

[Constraints, dependencies, performance concerns, or technology choices.]

Implementation Surface

Rails areas this feature will likely touch (no code — discovery only):

• controllers/ — [which controllers or new ones]
• models/ — [which models]
• services/ — [new service objects]
• jobs/ — [background jobs if any]
• mailers/ — [mailers if any]
• External integrations — [third-party services if any]

Success Metrics

• [How success is measured — quantitative or qualitative.]
• [Leading indicator or acceptance criterion.]

Open Questions

• [Question 1 — owner / deadline if known]
• [Question 2 — owner / deadline if known]

Next Steps

Recommended next step: generate-tasks — break this PRD into implementation tasks with TDD gates.

Alternative chain targets: ticket-planning (tracker-ready tickets), rails-architecture-review (structural concerns surfaced by the PRD), rails-engine-author (if the PRD scopes a mountable engine), rails-stack-conventions (stack alignment for a Rails feature).