/create-prp

Create PRP

Feature file: $ARGUMENTS

Generate a complete PRP for general feature implementation with thorough research. Ensure context is passed to the AI agent to enable self-validation and iterative refinement. Read the feature file first to understand what needs to be created, how the examples provided help, and any other considerations.

The AI agent only gets the context you are appending to the PRP and training data. Assuma the AI agent has access to the codebase and the same knowledge cutoff as you, so its important that your research findings are included or referenced in the PRP. The Agent has Websearch capabilities, so pass urls to documentation and examples.

Research Process

1. **Codebase Analysis**

• Search for similar features/patterns in the codebase
• Identify files to reference in PRP
• Note existing conventions to follow
• Check test patterns for validation approach

2. **External Research**

• Search for similar features/patterns online
• Library documentation (include specific URLs)
• Implementation examples (GitHub/StackOverflow/blogs)
• Best practices and common pitfalls

3. **User Clarification** (if needed)

• Specific patterns to mirror and where to find them?
• Integration requirements and where to find them?

PRP Generation

Using ./templates/prp_base.md as template:

Critical Context to Include and pass to the AI agent as part of the PRP

• **Documentation**: URLs with specific sections
• **Code Examples**: Real snippets from codebase
• **Gotchas**: Library quirks, version issues
• **Patterns**: Existing approaches to follow

Implementation Blueprint

• Start with pseudocode showing approach
• Reference real files for patterns
• Include error handling strategy
• list tasks to be completed to fullfill the PRP in the order they should be

completed

*** CRITICAL AFTER YOU ARE DONE RESEARCHING AND EXPLORING THE CODEBASE BEFORE YOU START WRITING THE PRP ***

*** ULTRATHINK ABOUT THE PRP AND PLAN YOUR APPROACH THEN START WRITING THE PRP

Plan Guidelines

• **No Backwards Compatibility**: Never design plans with backwards compatibility in mind unless the user explicitly requests it. If something is being replaced or changed, replace it completely. Avoid shims, fallbacks, re-exports, or compatibility layers.
• **Deprecated Code**: Do not deprecate code that we are no longer using as the result of this plan. Instead, include a section at the end to remove it.
• **Unit & Integration Tests**: Do not include unit tests or integration tests

---

Output

Save as: `tmp/YYYY-MM-DD-ENG-XXXX-description.md{feature-name}.md`

• Format: `YYYY-MM-DD-ENG-XXXX-description.md` where:
• YYYY-MM-DD is today's date
• description is a brief kebab-case description
• Examples:
• `2025-01-08-improve-error-handling.md`

Quality Checklist

• [ ] All necessary context included
• [ ] Validation gates are executable by AI
• [ ] References existing patterns
• [ ] Clear implementation path
• [ ] Error handling documented

Score the PRP on a scale of 1-10 (confidence level to succeed in one-pass implementation using claude codes)

Remember: The goal is one-pass implementation success through comprehensive context.