Skip to main content
Ask Replit to plan in plain language before implementation. Replit can recognize when planning helps and often proposes a plan proactively, without a separate mode. Simply asking Replit to plan is enough; /plan is an optional shortcut.

When to plan

Start with planning when you need to:
  • Explore different approaches before choosing one.
  • Break a complex project into smaller pieces.
  • Understand your codebase or compare technologies.
  • Clarify requirements, risks, and testing steps.
You can optionally use /plan to open the planning skill. Tell Replit explicitly if you want a plan without implementation.

When to build

Ask Replit to build when you know what you want and are ready for changes. Building can involve writing code, modifying files, and configuring services. For a small, well-defined fix, you can describe the change directly. For larger work, review a plan first.

Plan, review, then build

1

Ask for a plan

Describe your goal, constraints, and what should remain unchanged. You can ask in plain language or use /plan. Ask Replit to plan first and wait before implementing.
2

Review and refine

Check the scope, proposed changes, risks, and test plan. Ask Replit to revise anything that is unclear or too broad.
3

Ask Replit to build

Once the plan matches your intent, ask Replit to implement it. For separate work, explore background tasks.
4

Check the result

Test the changed behavior and compare it with the agreed plan. Use checkpoints to review or roll back project changes.

Example planning request

When you’re satisfied, follow up with a specific build request, such as:

Next steps

Plan with Replit

Explore approaches before implementation.

Effective prompting

Write clear requests for Replit.