# PRP: [Feature Name]

PRP = Product Requirements Prompt. Give this to your AI coding agent and watch it nail the implementation on the first try.

The difference between "AI wrote something that kinda works" and "AI wrote exactly what I wanted" is specificity. This template forces you to be specific.

## Context

What exists today? Why does this feature need to exist? Write 2-3 sentences. The AI needs to understand the problem, not just the solution.

## Requirements

### Must Have

These are non-negotiable. If any of these don't ship, the feature isn't done.

- [ ] [Requirement 1 — be specific about behavior, not just "it should work"]
- [ ] [Requirement 2]
- [ ] [Requirement 3]

### Nice to Have

Things that would be great but won't block shipping.

- [ ] [Optional enhancement 1]
- [ ] [Optional enhancement 2]

## Implementation Approach

### Files to Create

- `path/to/new-file.ts` — [one sentence: what this file does and why it needs to exist]
- `path/to/another-file.tsx` — [what it does]

### Files to Modify

- `path/to/existing-file.ts` — [what changes and why]
- `path/to/another-existing.tsx` — [what changes]

### Database Changes

- [Migration description, if any. If none, delete this section.]

## Code Patterns

Show the AI what your code looks like. One example is worth a paragraph of instructions.

```typescript
// Example: follow this pattern for the new code
export function newFeature(input: InputType): OutputType {
  // Match the patterns already in this codebase
  // The AI will copy this style
}
```

## Validation

How do you know it works? Don't just say "it should work." List the actual checks.

1. [Specific test case or command to run]
2. [Manual testing step — what to click, what to look for]
3. [Edge case to verify]

## Gotchas

Every project has landmines. List them here so the AI doesn't step on them.

- [Known issue, weird dependency, or edge case]
- [Something that looks obvious but breaks in practice]

---

**The premium PRP library** has 4 templates: Feature, Bug Fix, Refactor, and Integration. Each one has pre-built sections for error handling, API integration patterns, and rollback strategies. [Get it here →](#)