replit-plan
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseReplit Task Planner
Replit任务规划工具
Break down projects into iterative development phases with checkpoints optimized for Replit Agent's workflow.
将项目拆分为针对Replit Agent工作流优化的、带有检查点的迭代开发阶段。
When to Use
使用场景
- Converting a large project into manageable phases
- Planning checkpoint strategy for complex builds
- Creating iterative prompts from a PRD or idea
- Structuring work for Replit Agent's extended autonomy mode
- 将大型项目拆分为可管理的阶段
- 为复杂构建规划检查点策略
- 根据产品需求文档(PRD)或想法生成迭代式提示词
- 为Replit Agent的扩展自主模式规划工作结构
Replit Agent Modes
Replit Agent模式
Build Mode (Default)
构建模式(默认)
- Agent writes code directly
- Best for: Implementation, coding, fixing bugs
- Creates checkpoints automatically
- Agent直接编写代码
- 最适合:实现功能、编码、修复漏洞
- 自动创建检查点
Plan Mode
规划模式
- Agent discusses without modifying code
- Best for: Architecture decisions, exploring approaches, reviewing PRDs
- Free (no checkpoint charges)
- Agent仅进行讨论,不修改代码
- 最适合:架构决策、探索实现方案、评审PRD
- 免费(不收取检查点费用)
Edit Mode
编辑模式
- Agent makes targeted changes to specific files
- Best for: Precise modifications, refactoring specific sections
- Agent对特定文件进行针对性修改
- 最适合:精确调整、重构特定代码段
Checkpoint Strategy
检查点策略
Replit Agent creates checkpoints after each prompt. Effective planning means:
- One checkpoint = one logical unit of work
- Each phase should be testable independently
- Phases build on each other sequentially
- Rollback-friendly boundaries
Replit Agent会在每个提示词执行完成后创建检查点。有效的规划需遵循:
- 一个检查点 = 一个逻辑工作单元
- 每个阶段应可独立测试
- 阶段之间需按顺序逐步推进
- 设置便于回滚的边界
Task Breakdown Template
任务拆分模板
markdown
undefinedmarkdown
undefined[Project Name] - Development Plan
[项目名称] - 开发规划
Overview
概述
Project: [Brief description]
Total Phases: [Number]
Estimated Checkpoints: [Number]
项目: [简要描述]
总阶段数: [数量]
预计检查点数量: [数量]
Phase 1: [Phase Name]
阶段1:[阶段名称]
Goal: [One sentence describing what's achieved]
Dependencies: None (starting point)
目标: [一句话描述本阶段达成的成果]
依赖项: 无(初始阶段)
Tasks
任务
- [Specific task 1]
- [Specific task 2]
- [Specific task 3]
- [具体任务1]
- [具体任务2]
- [具体任务3]
Deliverables
交付成果
- [Testable outcome 1]
- [Testable outcome 2]
- [可测试成果1]
- [可测试成果2]
Prompt for Replit Agent
给Replit Agent的提示词
[Phase goal description]. Specifically:
1. [Task 1 with details]
2. [Task 2 with details]
3. [Task 3 with details]
Stop after completing these tasks so I can review before continuing.[阶段目标描述]。具体要求:
1. [带细节的任务1]
2. [带细节的任务2]
3. [带细节的任务3]
完成后停止,以便我在继续前进行评审。Verification Steps
验证步骤
- [How to verify task 1]
- [How to verify task 2]
- [如何验证任务1]
- [如何验证任务2]
Phase 2: [Phase Name]
阶段2:[阶段名称]
Goal: [One sentence]
Dependencies: Phase 1 complete
目标: [一句话描述]
依赖项: 阶段1完成
Tasks
任务
[...]
[...]
Prompt for Replit Agent
给Replit Agent的提示词
[...]
[...]
Rollback Points
回滚点
- After Phase 1: [What's safe to rollback to]
- After Phase 2: [What's safe to rollback to]
- 阶段1完成后:[可安全回滚到的状态]
- 阶段2完成后:[可安全回滚到的状态]
Risk Mitigation
风险缓解
| Risk | Phase | Mitigation |
|---|---|---|
| [Risk] | [Phase #] | [How to handle] |
undefined| 风险 | 阶段 | 缓解措施 |
|---|---|---|
| [风险] | [阶段编号] | [处理方式] |
undefinedProcedure
操作流程
Step 1: Understand the Project
步骤1:理解项目
Gather from user:
- What is being built?
- What are all the features/requirements?
- Any dependencies between features?
- Are there external integrations?
从用户处收集信息:
- 要构建的是什么?
- 所有功能/需求有哪些?
- 功能之间是否存在依赖关系?
- 是否有外部集成需求?
Step 2: Identify Natural Boundaries
步骤2:识别自然边界
Look for:
- Setup vs Features — Config/auth first, then features
- Independent Features — Features that don't depend on each other
- Dependent Features — Features that require others to exist
- Polish vs Core — Error handling, edge cases last
重点关注:
- 设置与功能 — 先完成配置/认证,再开发功能
- 独立功能 — 互不依赖的功能
- 依赖功能 — 需基于其他功能才能存在的功能
- 优化与核心 — 错误处理、边缘情况放在最后
Step 3: Create Phases
步骤3:创建阶段
Phase 1: Foundation
Always start with:
- Project setup
- Database schema
- Authentication (if needed)
- Basic navigation/layout
Phase 2-N: Core Features
Group related functionality:
- One major feature per phase
- Include its UI, API, and data needs
- Keep phases 30-60 minutes of Agent work
Final Phase: Polish
Always end with:
- Error handling
- Loading states
- Edge cases
- Responsive fixes
- Final testing
阶段1:基础搭建
始终从以下内容开始:
- 项目初始化
- 数据库schema设计
- 认证功能(如有需要)
- 基础导航/布局
阶段2至N:核心功能
将相关功能分组:
- 每个阶段对应一个主要功能
- 包含该功能的UI、API和数据需求
- 每个阶段的Agent工作时长控制在30-60分钟
最终阶段:优化完善
始终以以下内容收尾:
- 错误处理
- 加载状态
- 边缘情况
- 响应式修复
- 最终测试
Step 4: Write Prompts for Each Phase
步骤4:为每个阶段编写提示词
Each prompt should:
- State the goal clearly
- List specific tasks (numbered)
- Include technical details
- Request a stop point for review
Template:
Implement [Feature Name].
Requirements:
1. [Specific requirement with details]
2. [Specific requirement with details]
3. [Specific requirement with details]
Technical notes:
- [Relevant constraint or approach]
- [Relevant constraint or approach]
Create a checkpoint when complete so I can review before the next phase.每个提示词应包含:
- 清晰说明目标
- 列出具体的编号任务
- 包含技术细节
- 请求设置停止点以便评审
模板:
实现[功能名称]。
需求:
1. [带细节的具体需求1]
2. [带细节的具体需求2]
3. [带细节的具体需求3]
技术说明:
- [相关约束或实现方案]
- [相关约束或实现方案]
完成后创建检查点,以便我在下一阶段前进行评审。Step 5: Define Verification Steps
步骤5:定义验证步骤
For each phase, include how to verify:
- What to click/test in the UI
- What API calls to make
- What database records to check
为每个阶段明确验证方式:
- 在UI中点击/测试哪些内容
- 调用哪些API
- 检查哪些数据库记录
Step 6: Present the Plan
步骤6:呈现规划
undefinedundefinedDevelopment Plan: [Project Name]
开发规划:[项目名称]
Phases: [Number]
Approach: [Brief strategy explanation]
[Full plan with all phases]
阶段数: [数量]
实现方案: [简要策略说明]
[包含所有阶段的完整规划]
How to Use This Plan
如何使用本规划
- Start with Plan Mode: Copy Phase 1 prompt, select Plan Mode
- Review Agent's approach: Ensure it aligns with expectations
- Switch to Build Mode: Approve and let Agent implement
- Verify at checkpoint: Test deliverables before continuing
- Proceed to next phase: Copy next prompt and repeat
- 从规划模式开始:复制阶段1的提示词,选择规划模式
- 评审Agent的方案:确保与预期一致
- 切换到构建模式:确认后让Agent执行实现
- 在检查点验证:继续前测试交付成果
- 推进到下一阶段:复制下一个提示词并重复流程
Iteration Strategy
迭代策略
If issues arise:
- Minor issues: Describe and ask Agent to fix in current phase
- Major issues: Rollback to previous checkpoint, refine prompt, retry
Ready to start?
undefined若出现问题:
- 小问题:描述问题并要求Agent在当前阶段修复
- 大问题:回滚到上一个检查点,优化提示词后重试
准备开始了吗?
undefinedPhase Sizing Guidelines
阶段规模指南
| Phase Size | Work Amount | Example |
|---|---|---|
| Small | 15-30 min | Add a single form with validation |
| Medium | 30-60 min | Full CRUD for one entity |
| Large | 60-90 min | Feature with UI + API + data |
Ideal phase: Medium (30-60 minutes)
Signs phase is too large:
- More than 5 major tasks
- Touches more than 4-5 files
- Multiple unrelated features
- "Build the entire X" language
Signs phase is too small:
- Single task that takes < 10 minutes
- No testable deliverable
- Could easily be combined with adjacent phase
| 阶段规模 | 工作量 | 示例 |
|---|---|---|
| 小型 | 15-30分钟 | 添加带验证的单个表单 |
| 中型 | 30-60分钟 | 单个实体的完整CRUD功能 |
| 大型 | 60-90分钟 | 包含UI + API + 数据的功能 |
理想阶段: 中型(30-60分钟)
阶段过大的迹象:
- 超过5个主要任务
- 涉及4-5个以上文件
- 包含多个不相关功能
- 出现“构建整个X”的表述
阶段过小的迹象:
- 单个任务耗时<10分钟
- 无可测试的交付成果
- 可轻松与相邻阶段合并
Common Phase Patterns
常见阶段模式
Pattern 1: CRUD Feature
模式1:CRUD功能
Phase N: [Entity] Management
1. Database model and migrations
2. API endpoints (list, create, read, update, delete)
3. List view with table/cards
4. Create/edit form (modal or page)
5. Delete with confirmation
Deliverables:
- [ ] Can create new [entity]
- [ ] Can view list of [entities]
- [ ] Can edit existing [entity]
- [ ] Can delete [entity]阶段N:[实体]管理
1. 数据库模型与迁移
2. API端点(列表、创建、读取、更新、删除)
3. 带表格/卡片的列表视图
4. 创建/编辑表单(模态框或页面)
5. 带确认的删除功能
交付成果:
- [ ] 可创建新的[实体]
- [ ] 可查看[实体]列表
- [ ] 可编辑现有[实体]
- [ ] 可删除[实体]Pattern 2: Authentication
模式2:认证功能
Phase 1: Authentication Setup
1. Configure auth provider (Supabase/Clerk/etc.)
2. Create signup page with form
3. Create login page with form
4. Add protected route wrapper
5. Add user context/hook
6. Add logout functionality
Deliverables:
- [ ] New user can sign up
- [ ] Existing user can log in
- [ ] Protected pages redirect to login
- [ ] User can log out阶段1:认证设置
1. 配置认证提供商(Supabase/Clerk等)
2. 创建带表单的注册页面
3. 创建带表单的登录页面
4. 添加受保护路由包装器
5. 添加用户上下文/钩子
6. 添加登出功能
交付成果:
- [ ] 新用户可注册
- [ ] 现有用户可登录
- [ ] 受保护页面会重定向到登录页
- [ ] 用户可登出Pattern 3: Dashboard
模式3:仪表盘
Phase N: Dashboard
1. Create dashboard layout
2. Add metric cards with data fetching
3. Add recent activity list
4. Add quick action buttons
5. Implement responsive grid
Deliverables:
- [ ] Dashboard loads with correct data
- [ ] Metrics update when data changes
- [ ] Recent activity shows latest items
- [ ] Layout works on mobile阶段N:仪表盘
1. 创建仪表盘布局
2. 添加带数据获取的指标卡片
3. 添加最近活动列表
4. 添加快速操作按钮
5. 实现响应式网格
交付成果:
- [ ] 仪表盘加载正确数据
- [ ] 数据变化时指标更新
- [ ] 最近活动显示最新条目
- [ ] 布局在移动端正常显示Pattern 4: External Integration
模式4:外部集成
Phase N: [Service] Integration
1. Set up environment variables for API keys
2. Create service wrapper/client
3. Implement core integration function
4. Add error handling for API failures
5. Connect to UI trigger point
Deliverables:
- [ ] API key configuration works
- [ ] Integration function returns expected data
- [ ] Errors handled gracefully
- [ ] UI reflects integration state阶段N:[服务]集成
1. 设置API密钥的环境变量
2. 创建服务包装器/客户端
3. 实现核心集成功能
4. 添加API失败的错误处理
5. 连接到UI触发点
交付成果:
- [ ] API密钥配置生效
- [ ] 集成功能返回预期数据
- [ ] 错误得到优雅处理
- [ ] UI反映集成状态Example: Full Task Breakdown
示例:完整任务拆分
Project: Todo App with Categories
项目:带分类的待办事项应用
markdown
undefinedmarkdown
undefinedTodo App - Development Plan
待办事项应用 - 开发规划
Overview
概述
Project: Todo app with categories, due dates, and search
Total Phases: 4
Estimated Checkpoints: 5
项目: 带分类、截止日期和搜索功能的待办事项应用
总阶段数: 4
预计检查点数量: 5
Phase 1: Foundation
阶段1:基础搭建
Goal: Set up project with database and basic structure
Dependencies: None
目标: 完成项目初始化与数据库及基础结构搭建
依赖项: 无
Tasks
任务
- Initialize React + Vite project with TailwindCSS
- Set up SQLite database with Prisma
- Create Todo and Category models
- Set up Express API with basic structure
- Create app shell with header and main area
- 初始化React + Vite项目并集成TailwindCSS
- 配置SQLite数据库与Prisma
- 创建Todo和Category模型
- 搭建Express API基础结构
- 创建带头部和主区域的应用框架
Deliverables
交付成果
- Project runs without errors
- Database creates successfully
- Empty app shell renders
- 项目可正常运行无错误
- 数据库创建成功
- 空应用框架可正常渲染
Prompt
提示词
Set up a Todo app with React, Vite, TailwindCSS, Express, and SQLite with Prisma.
1. Initialize React + Vite project
2. Add TailwindCSS configuration
3. Create Express backend with /api prefix
4. Set up Prisma with SQLite
5. Create models:
- Category: id (uuid), name (string), color (string)
- Todo: id (uuid), title (string), completed (boolean), due_date (date nullable), category_id (uuid nullable, FK)
6. Create basic app layout with header showing "Todo App"
Stop when the shell runs and database migrates successfully.搭建一个使用React、Vite、TailwindCSS、Express和SQLite + Prisma的待办事项应用。
1. 初始化React + Vite项目
2. 添加TailwindCSS配置
3. 创建带/api前缀的Express后端
4. 配置Prisma与SQLite
5. 创建模型:
- Category: id (uuid), name (string), color (string)
- Todo: id (uuid), title (string), completed (boolean), due_date (date nullable), category_id (uuid nullable, FK)
6. 创建基础应用布局,头部显示“Todo App”
当应用框架可运行且数据库迁移完成后停止。Phase 2: Category Management
阶段2:分类管理
Goal: Full CRUD for categories
Dependencies: Phase 1
目标: 完成分类的完整CRUD功能
依赖项: 阶段1完成
Tasks
任务
- API endpoints for categories
- Category list sidebar
- Add/edit category modal
- Delete category with confirmation
- Color picker for categories
- 分类的API端点
- 分类列表侧边栏
- 添加/编辑分类的模态框
- 带确认的分类删除功能
- 分类颜色选择器
Deliverables
交付成果
- Can create category with name and color
- Categories display in sidebar
- Can edit category
- Can delete category
- 可创建带名称和颜色的分类
- 分类显示在侧边栏
- 可编辑分类
- 可删除分类
Prompt
提示词
Implement category management for the Todo app.
1. Create API endpoints:
- GET /api/categories - list all
- POST /api/categories - create new
- PUT /api/categories/:id - update
- DELETE /api/categories/:id - delete
2. Create sidebar showing category list with colored dots
3. Add "New Category" button that opens modal
4. Modal has: name input, color picker (preset colors), save/cancel
5. Category item has edit and delete buttons
6. Delete shows confirmation before removing
Use a simple color picker with 8 preset colors.
Stop when categories can be created, edited, and deleted.为待办事项应用实现分类管理功能。
1. 创建API端点:
- GET /api/categories - 获取所有分类
- POST /api/categories - 创建新分类
- PUT /api/categories/:id - 更新分类
- DELETE /api/categories/:id - 删除分类
2. 创建显示分类列表的侧边栏,每个分类带彩色圆点
3. 添加“新建分类”按钮,点击打开模态框
4. 模态框包含:名称输入框、颜色选择器(预设颜色)、保存/取消按钮
5. 分类项带编辑和删除按钮
6. 删除操作需先显示确认提示
使用包含8种预设颜色的简单颜色选择器。
当分类可创建、编辑和删除后停止。Phase 3: Todo Management
阶段3:待办事项管理
Goal: Full todo functionality with categories and due dates
Dependencies: Phase 2
目标: 完成带分类和截止日期的完整待办事项功能
依赖项: 阶段2完成
Tasks
任务
- API endpoints for todos
- Todo list component with checkboxes
- Add todo form
- Edit todo modal
- Category assignment dropdown
- Due date picker
- Filter todos by category (click sidebar)
- 待办事项的API端点
- 带复选框的待办事项列表组件
- 添加待办事项的表单
- 编辑待办事项的模态框
- 分类分配下拉框
- 截止日期选择器
- 按分类筛选待办事项(点击侧边栏)
Deliverables
交付成果
- Can create todo with optional category and due date
- Can mark todo complete/incomplete
- Can edit todo details
- Can delete todo
- Clicking category filters todos
- 可创建带可选分类和截止日期的待办事项
- 可标记待办事项完成/未完成
- 可编辑待办事项详情
- 可删除待办事项
- 点击侧边栏分类可筛选待办事项
Prompt
提示词
Implement todo management with category assignment and due dates.
1. Create API endpoints:
- GET /api/todos?category_id=x - list todos, optional filter
- POST /api/todos - create
- PUT /api/todos/:id - update
- DELETE /api/todos/:id - delete
2. Main area shows todo list:
- Checkbox to toggle complete (strikethrough when done)
- Title text
- Category badge (colored)
- Due date badge (red if overdue)
- Edit/delete buttons on hover
3. Add todo form at top:
- Title input (required)
- Category dropdown (optional)
- Due date picker (optional)
4. Click category in sidebar to filter todos (highlight selected)
5. Edit todo opens modal with all fields editable
Sort todos: incomplete first, then by due date (soonest first).
Stop when todos can be fully managed with categories and dates.实现带分类分配和截止日期的待办事项管理功能。
1. 创建API端点:
- GET /api/todos?category_id=x - 获取待办事项,支持可选筛选
- POST /api/todos - 创建待办事项
- PUT /api/todos/:id - 更新待办事项
- DELETE /api/todos/:id - 删除待办事项
2. 主区域显示待办事项列表:
- 复选框用于切换完成状态(完成时显示删除线)
- 标题文本
- 彩色分类标签
- 截止日期标签(逾期时显示红色)
- hover时显示编辑/删除按钮
3. 顶部添加待办事项表单:
- 标题输入框(必填)
- 分类下拉框(可选)
- 截止日期选择器(可选)
4. 点击侧边栏分类可筛选待办事项(选中项高亮)
5. 编辑待办事项会打开模态框,所有字段均可编辑
待办事项排序:未完成事项优先,然后按截止日期排序(最近的在前)。
当待办事项可通过分类和日期进行完整管理后停止。Phase 4: Search and Polish
阶段4:搜索与体验优化
Goal: Add search and polish UX
Dependencies: Phase 3
目标: 添加搜索功能并优化用户体验
依赖项: 阶段3完成
Tasks
任务
- Search input in header
- Search filters todos by title (client-side)
- Empty states for no todos / no results
- Loading states
- Error handling with toast messages
- Responsive design adjustments
- 头部添加搜索输入框
- 搜索功能按标题筛选待办事项(客户端)
- 无待办事项/无搜索结果的空状态
- 加载状态
- 带提示消息的错误处理
- 响应式设计调整
Deliverables
交付成果
- Search filters todos in real-time
- Empty states display appropriately
- Errors show user-friendly messages
- Works on mobile screens
- 搜索可实时筛选待办事项
- 空状态正确显示
- 错误显示友好的用户提示
- 在移动端正常运行
Prompt
提示词
Add search functionality and polish the UX.
1. Add search input in header (right side)
2. Search filters todos by title (case-insensitive, client-side)
3. Add empty states:
- No todos: "No todos yet. Add one above!"
- No results: "No todos match your search"
- No category selected + no todos: "Select a category or add a todo"
4. Add loading spinner for initial data fetch
5. Add error toast for API failures
6. Responsive adjustments:
- Mobile: hide sidebar, add hamburger menu
- Sidebar overlays on mobile when menu open
Test all flows and fix any visual issues.
This is the final phase - ensure everything works smoothly.添加搜索功能并优化用户体验。
1. 头部右侧添加搜索输入框
2. 搜索按标题筛选待办事项(不区分大小写,客户端实现)
3. 添加空状态:
- 无待办事项:“还没有待办事项,上方添加一个吧!”
- 无搜索结果:“没有匹配的待办事项”
- 未选择分类且无待办事项:“选择一个分类或添加待办事项”
4. 初始数据加载时添加加载动画
5. API失败时添加错误提示 toast
6. 响应式调整:
- 移动端:隐藏侧边栏,添加汉堡菜单
- 点击菜单时侧边栏在移动端覆盖显示
测试所有流程并修复视觉问题。
这是最终阶段 - 确保所有功能运行流畅。Rollback Points
回滚点
- After Phase 1: Clean slate with just structure
- After Phase 2: Categories work, can redo todo implementation
- After Phase 3: Full functionality, can redo polish
- 阶段1完成后:仅包含基础结构的干净状态
- 阶段2完成后:分类功能正常,可重新实现待办事项部分
- 阶段3完成后:功能完整,可重新进行优化
Risk Mitigation
风险缓解
| Risk | Phase | Mitigation |
|---|---|---|
| Prisma schema issues | 1 | Test migration before proceeding |
| Filter state complexity | 3 | Use URL params for filter state |
| Mobile responsive issues | 4 | Test each breakpoint individually |
undefined| 风险 | 阶段 | 缓解措施 |
|---|---|---|
| Prisma schema问题 | 1 | 继续前测试迁移 |
| 筛选状态复杂度 | 3 | 使用URL参数管理筛选状态 |
| 移动端响应式问题 | 4 | 逐个测试断点 |
undefinedOutput Format
输出格式
undefinedundefinedDevelopment Plan: [Project Name]
开发规划:[项目名称]
Summary
摘要
| Metric | Value |
|---|---|
| Total Phases | [Number] |
| Estimated Build Time | [Range] |
| Checkpoint Strategy | [Brief] |
[Phase-by-phase breakdown with prompts]
| 指标 | 数值 |
|---|---|
| 总阶段数 | [数量] |
| 预计构建时长 | [范围] |
| 检查点策略 | [简要说明] |
[带提示词的分阶段详细规划]
Quick Reference
快速参考
Phase Prompts (Copy-Paste Ready)
阶段提示词(可直接复制)
Phase 1:
[Prompt]Phase 2:
[Prompt][Continue for all phases]
阶段1:
[提示词]阶段2:
[提示词][所有阶段依次列出]
Verification Checklist
验证清单
After each phase, verify:
- Phase 1: [Key items]
- Phase 2: [Key items] [...]
Ready to begin?
undefined每个阶段完成后验证:
- 阶段1:[关键项]
- 阶段2:[关键项] [...]
准备开始了吗?
undefinedRules
规则
- ALWAYS start with foundation phase — Setup, schema, auth first
- ALWAYS end with polish phase — Error handling, edge cases last
- ALWAYS include verification steps — Testable deliverables per phase
- ALWAYS size phases appropriately — 30-60 minutes ideal
- NEVER combine unrelated features — One major feature per phase
- NEVER skip rollback planning — Document safe rollback points
- PREFER explicit prompts — Include technical details in each phase prompt
- 始终从基础搭建阶段开始 — 先完成设置、schema、认证
- 始终以优化完善阶段收尾 — 错误处理、边缘情况放在最后
- 始终包含验证步骤 — 每个阶段都要有可测试的交付成果
- 始终合理设置阶段规模 — 理想时长30-60分钟
- 切勿合并不相关功能 — 每个阶段对应一个主要功能
- 切勿跳过回滚规划 — 记录可安全回滚的节点
- 优先使用明确的提示词 — 每个阶段的提示词包含技术细节