Your First Workflow¶
You've installed rp1. Now let's put it to work.
Choose Your Path¶
You have an existing project and want rp1 to learn it. Continue below to build your knowledge base.
You're creating a brand new project from scratch (a "greenfield" project - starting with a clean slate, no existing code).
The bootstrap workflow will guide you through project creation with charter interviews, tech stack selection, and scaffolding.
Build Your Knowledge Base¶
The first step with any existing codebase is building a knowledge base. This teaches rp1 about your project's structure, architecture, and patterns.
Expected Output¶
After the command completes, you'll see:
or for a single project:
What Just Happened?¶
The knowledge-build command analyzed your codebase and created knowledge base files in .rp1/context/.
KB File Reference
See What's in the Knowledge Base? for the complete list of generated files and their purposes.
Future rp1 commands use this knowledge base to understand your codebase context, making their outputs more accurate and relevant.
Incremental Updates
First builds take 10-15 minutes for large projects. Subsequent runs are incremental and complete in 2-5 minutes.
Ready to Ship? Start Here¶
The recommended next step is to build a feature. This is rp1's flagship workflow - from requirements to deployed code.
Explore More Workflows¶
Now that rp1 understands your codebase, try these workflows:
-
Start a New Feature
Create a charter and PRD for a new project or feature.
/blueprint -
Build a Feature
Full workflow from requirements to verified implementation.
/build my-feature -
Quick Task
Small fixes or enhancements under 2 hours.
/build-fast "Add dark mode toggle" -
Review a Pull Request
Get structured feedback on code changes.
/pr-review