steve
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSteve — wavybaby + GSD + Ralph Autonomous Execution
Steve — wavybaby + GSD + Ralph 自主执行流程
Combines three systems:
- wavybaby: Self-equipping toolchain (CoVe verification, skill discovery via skills.sh, MCP server setup, project config)
- GSD: Structured project management (, roadmaps, phases, plans, discovery, verification, state tracking)
.planning/ - Ralph: Autonomous while-true loop (circuit breakers, dual-condition exit, session persistence, rate limiting)
The result: describe what you want. Steve equips itself with the best tools for the job, generates a PRD, builds a full GSD project structure, and runs an autonomous loop that executes every plan with verified code until the milestone is done.
User's description
|
v
PHASE 0: Equip (wavybaby)
| - Detect project type and stack
| - Search skills.sh for relevant skills, install missing ones
| - Install missing MCP servers (Context7, Supabase, Sentry, etc.)
| - Set up project config (settings.local.json, CLAUDE.md)
| - Now the agent has the best tools for THIS specific project
|
v
PHASE 1: PRD Generation
| - Clarifying questions
| - Full PRD at .planning/specs/PRD.md
|
v
PHASE 2: GSD Project Bootstrap
| - PROJECT.md, ROADMAP.md, STATE.md, config.json
| - codebase/ docs (STACK, ARCHITECTURE, STRUCTURE, CONVENTIONS)
| - Phase directories with DISCOVERY.md per phase
|
v
PHASE 3: Plan Generation
| - Break each phase into {NN}-{NN}-PLAN.md files
| - Each plan: 1-4 hours, atomic, with verification steps
|
v
PHASE 4: Loop Configuration
| - .ralphrc tuned for GSD execution
| - PROMPT.md with GSD execution + CoVe verification logic
| - AGENT.md with build/test/lint commands
|
v
PHASE 5: Autonomous Execution
- ralph --monitor
- Each loop iteration: read STATE.md -> execute next plan (with CoVe on non-trivial code) -> write SUMMARY.md -> update STATE.md
- Circuit breaker halts if stuck
- Exits when all phases complete整合三大系统:
- wavybaby:自适配工具链(CoVe验证、通过skills.sh发现技能、MCP服务器搭建、项目配置)
- GSD:结构化项目管理(目录、路线图、阶段划分、计划制定、需求调研、验证、状态跟踪)
.planning/ - Ralph:自主循环执行框架(断路器机制、双条件退出、会话持久化、速率限制)
实现效果:只需描述你的需求。Steve会为任务配备最优工具,生成PRD,搭建完整的GSD项目结构,然后启动自主循环,执行所有计划并通过代码验证,直至完成里程碑目标。
用户需求描述
|
v
阶段0:工具适配(wavybaby)
| - 检测项目类型与技术栈
| - 搜索skills.sh获取相关技能,安装缺失项
| - 安装缺失的MCP服务器(Context7、Supabase、Sentry等)
| - 配置项目参数(settings.local.json、CLAUDE.md)
| - 至此,Agent已为当前项目配备最优工具
|
v
阶段1:PRD生成
| - 需求澄清提问
| - 在.planning/specs/PRD.md生成完整PRD
|
v
阶段2:GSD项目初始化
| - 生成PROJECT.md、ROADMAP.md、STATE.md、config.json
| - 生成codebase/文档(STACK、ARCHITECTURE、STRUCTURE、CONVENTIONS)
| - 为每个阶段创建目录并生成DISCOVERY.md
|
v
阶段3:计划拆分
| - 将每个阶段拆分为{NN}-{NN}-PLAN.md文件
| - 每个计划:耗时1-4小时,原子化,包含验证步骤
|
v
阶段4:循环配置
| - 针对GSD执行优化.ralphrc配置
| - 生成包含GSD执行逻辑与CoVe验证规则的PROMPT.md
| - 生成包含构建/测试/检查命令的AGENT.md
|
v
阶段5:自主执行
- 运行ralph --monitor
- 每次循环迭代:读取STATE.md → 执行下一个计划(非 trivial 代码需经过CoVe验证)→ 写入SUMMARY.md → 更新STATE.md
- 若陷入停滞,断路器机制会终止执行
- 所有阶段完成后自动退出PHASE 0: EQUIP (wavybaby)
阶段0:工具适配(wavybaby)
Before generating anything, equip the agent with the best tools for this specific project. This is what separates Steve from raw GSD+Ralph — the agent isn't flying blind.
在生成任何内容前,先为Agent适配当前项目的最优工具。这是Steve区别于原生GSD+Ralph的核心优势——Agent不会盲目执行任务。
Step 1: Detect project type
步骤1:检测项目类型
Scan for: , , , , , , , . Determine:
package.jsonpyproject.tomlCargo.tomlgo.modGemfilepubspec.yamlPodfilebuild.gradle- Language(s)
- Framework(s)
- Package manager
- Existing dependencies
扫描以下文件:、、、、、、、。确定:
package.jsonpyproject.tomlCargo.tomlgo.modGemfilepubspec.yamlPodfilebuild.gradle- 使用的编程语言
- 采用的框架
- 包管理器
- 已有的依赖项
Step 2: Search and install relevant skills
步骤2:搜索并安装相关技能
bash
undefinedbash
undefinedSearch skills.sh for skills matching the detected stack
根据检测到的技术栈在skills.sh中搜索技能
npx skills find "[detected framework]"
npx skills find "[detected language]"
npx skills find "[project domain from user description]"
**Auto-install recommendations based on stack:**
| Stack | Skills to Install |
|-------|------------------|
| React / Next.js | `npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices --agent claude-code -y` |
| React Native / Expo | `npx skills add expo/skills --agent claude-code -y` |
| Supabase | `npx skills add supabase/agent-skills --agent claude-code -y` |
| Stripe payments | `npx skills add stripe/skills --agent claude-code -y` |
| Cloudflare | `npx skills add cloudflare/skills --agent claude-code -y` |
| Any web project | `npx skills add vercel-labs/agent-skills --skill web-design-guidelines --agent claude-code -y` |
| Security-critical | `npx skills add trailofbits/skills --agent claude-code -y` |
Install all relevant skills immediately — don't ask, just do it. The `-y` flag auto-confirms.npx skills find "[检测到的框架]"
npx skills find "[检测到的语言]"
npx skills find "[用户需求中的项目领域]"
**基于技术栈的自动安装推荐:**
| 技术栈 | 需安装的技能 |
|-------|------------------|
| React / Next.js | `npx skills add vercel-labs/agent-skills --skill vercel-react-best-practices --agent claude-code -y` |
| React Native / Expo | `npx skills add expo/skills --agent claude-code -y` |
| Supabase | `npx skills add supabase/agent-skills --agent claude-code -y` |
| Stripe 支付 | `npx skills add stripe/skills --agent claude-code -y` |
| Cloudflare | `npx skills add cloudflare/skills --agent claude-code -y` |
| 任意Web项目 | `npx skills add vercel-labs/agent-skills --skill web-design-guidelines --agent claude-code -y` |
| 安全敏感项目 | `npx skills add trailofbits/skills --agent claude-code -y` |
直接安装所有相关技能——无需询问,直接执行。`-y`参数用于自动确认安装。Step 3: Install missing MCP servers
步骤3:安装缺失的MCP服务器
Check which MCP servers are already configured, then install all relevant ones directly:
| Server | When to Install | Command |
|---|---|---|
| Context7 | Always (prevents doc hallucinations) | |
| GitHub | If using GitHub | |
| Supabase | If Supabase in stack | |
| Sentry | If error tracking needed | |
| Notion | If docs workflow | |
| Sequential Thinking | Complex architecture | |
检查已配置的MCP服务器,然后直接安装所有相关服务器:
| 服务器 | 安装场景 | 命令 |
|---|---|---|
| Context7 | 所有项目(避免文档幻觉) | |
| GitHub | 使用GitHub的项目 | |
| Supabase | 技术栈包含Supabase的项目 | |
| Sentry | 需要错误追踪的项目 | |
| Notion | 涉及Notion文档流程的项目 | |
| Sequential Thinking | 复杂架构项目 | |
Step 4: Set up project config
步骤4:配置项目参数
If missing, create with appropriate permissions:
settings.local.jsonFull-Stack (Node/React):
json
{
"permissions": {
"allow": [
"WebSearch",
"Bash(npm *)", "Bash(pnpm *)",
"Bash(git *)", "Bash(gh *)",
"Bash(docker *)",
"mcp__plugin_context7_context7__*",
"Skill(*)"
]
}
}Python:
json
{
"permissions": {
"allow": [
"Bash(python *)", "Bash(pip *)", "Bash(poetry *)",
"Bash(pytest *)", "Bash(docker-compose *)",
"Bash(git *)"
]
}
}Adjust per detected stack.
若不存在则创建,并设置相应权限:
settings.local.json全栈项目(Node/React):
json
{
"permissions": {
"allow": [
"WebSearch",
"Bash(npm *)", "Bash(pnpm *)",
"Bash(git *)", "Bash(gh *)",
"Bash(docker *)",
"mcp__plugin_context7_context7__*",
"Skill(*)"
]
}
}Python项目:
json
{
"permissions": {
"allow": [
"Bash(python *)", "Bash(pip *)", "Bash(poetry *)",
"Bash(pytest *)", "Bash(docker-compose *)",
"Bash(git *)"
]
}
}根据检测到的技术栈调整配置。
Step 5: Report equip status
步骤5:报告适配状态
Equipped for: [project type]
Skills installed:
- [skill 1] (from [repo])
- [skill 2] (from [repo])
MCP servers configured:
- [server 1]: [purpose]
- [server 2]: [purpose]
Project config: settings.local.json [created/updated/already exists]已适配项目类型:[项目类型]
已安装技能:
- [技能1](来自[仓库])
- [技能2](来自[仓库])
已配置MCP服务器:
- [服务器1]:[用途]
- [服务器2]:[用途]
项目配置:settings.local.json [已创建/已更新/已存在]PHASE 1: PRD GENERATION
阶段1:PRD生成
Deep-dive questioning (MANDATORY)
深度需求调研(必填)
Before writing the PRD, conduct a thorough interview. Ask questions in multiple rounds using AskUserQuestion. Do NOT rush to generate the PRD — the quality of the PRD depends entirely on how well you understand the project. Keep asking until you have a clear picture.
Round 1: Vision & Users
- "What problem does this solve? What's the pain point today?"
- "Who are the primary users? Describe 2-3 distinct personas."
- "What does success look like? How will you know this is working?"
- "Are there existing products/competitors? What do they get wrong?"
Round 2: Core Experience
- "Walk me through the ideal user journey from first open to daily use."
- "What are the 3 features that MUST exist for this to be useful? What's the single most important one?"
- "What should the user feel when using this? (fast, calm, powerful, fun, simple)"
- "Are there any workflows that need to feel instant vs. ones that can load?"
Round 3: Technical & Platform
- "What's the target platform? (iOS, Android, both, web, desktop, CLI)"
- "Any existing backend, database, auth system, or APIs to integrate with?"
- "Do you have preferences on stack/framework, or should I recommend?"
- "Does this need real-time features? (live updates, collaboration, notifications)"
- "Offline support needed? What should work without internet?"
- "Any third-party services? (payments, maps, analytics, AI/ML, messaging)"
Round 4: Data & Business Logic
- "What are the core entities/objects in this system? (users, posts, orders, etc.)"
- "What are the key relationships between them? (a user has many X, an X belongs to Y)"
- "Are there different user roles or permission levels? Describe each."
- "Any complex business rules? (pricing tiers, approval workflows, calculations)"
- "What data is sensitive? (PII, financial, health)"
Round 5: Scope & Constraints
- "What's MVP vs. nice-to-have vs. definitely-not-now?"
- "Any hard deadlines or constraints?"
- "Any design preferences? (dark mode, specific brand colors, reference apps you love)"
- "What about accessibility? (screen reader support, color blindness, motor impairment)"
- "Internationalization needed? Which languages/locales?"
- "Any compliance requirements? (GDPR, HIPAA, SOC2, PCI)"
Round 6: Edge Cases & Polish
- "What happens when something goes wrong? (no internet, server error, invalid input)"
- "What empty states exist? (new user, no data yet, search with no results)"
- "What notifications/emails/alerts should the system send?"
- "Onboarding flow — how does a new user learn the app?"
- "Any admin/backoffice needs? (dashboards, moderation, analytics)"
You do NOT need to ask every single question. Skip ones that are obviously irrelevant to the project. But you MUST ask across at least 4 of these 6 rounds. Use your judgment — if the user's description is vague, ask more. If it's detailed, focus on gaps.
After each round, acknowledge what you've learned and explain what you still need to know before asking the next round. Stop when you have enough to write a comprehensive PRD.
在编写PRD前,需进行全面的需求沟通。使用AskUserQuestion进行多轮提问。切勿急于生成PRD——PRD的质量完全取决于对项目的理解程度。持续提问直至清晰掌握项目需求。
第一轮:愿景与用户
- "该项目解决什么问题?当前的痛点是什么?"
- "主要用户群体是谁?请描述2-3个典型用户画像。"
- "成功的标准是什么?如何衡量项目是否成功?"
- "是否有同类产品或竞争对手?他们存在哪些不足?"
第二轮:核心体验
- "请描述从首次使用到日常操作的理想用户流程。"
- "哪些功能是项目必备的?其中最重要的功能是什么?"
- "用户使用该产品时应获得怎样的感受?(快速、安心、强大、有趣、简洁)"
- "哪些流程需要即时响应?哪些可以接受加载延迟?"
第三轮:技术与平台
- "目标平台是什么?(iOS、Android、双端、Web、桌面端、CLI)"
- "是否需要集成现有后端、数据库、认证系统或API?"
- "你对技术栈/框架有偏好,还是需要我推荐?"
- "是否需要实时功能?(实时更新、协作、通知)"
- "是否需要离线支持?离线状态下哪些功能需正常可用?"
- "是否需要集成第三方服务?(支付、地图、分析、AI/ML、消息推送)"
第四轮:数据与业务逻辑
- "系统中的核心实体/对象有哪些?(用户、帖子、订单等)"
- "这些实体之间的关键关系是什么?(一个用户拥有多个X,X属于Y)"
- "是否存在不同的用户角色或权限等级?请描述每个角色的权限。"
- "是否有复杂的业务规则?(定价 tiers、审批流程、计算逻辑)"
- "哪些数据属于敏感数据?(个人身份信息、财务数据、健康数据)"
第五轮:范围与约束
- "MVP版本、锦上添花功能、暂不考虑功能分别包含哪些内容?"
- "是否有硬性截止日期或其他约束条件?"
- "是否有设计偏好?(深色模式、特定品牌色、你喜欢的参考应用)"
- "是否需要考虑无障碍设计?(屏幕阅读器支持、色盲友好、肢体障碍适配)"
- "是否需要国际化支持?支持哪些语言/地区?"
- "是否有合规要求?(GDPR、HIPAA、SOC2、PCI)"
第六轮:边缘情况与细节打磨
- "出现异常情况时应如何处理?(无网络、服务器错误、无效输入)"
- "存在哪些空状态场景?(新用户、无数据、搜索无结果)"
- "系统应发送哪些通知/邮件/提醒?"
- "新用户引导流程如何设计?用户如何学习使用应用?"
- "是否需要管理员/后台功能?(仪表盘、内容审核、数据分析)"
无需询问所有问题,可跳过与项目明显无关的问题。但必须覆盖至少4个轮次的提问。根据实际情况判断:若用户描述模糊,则增加提问;若描述详细,则聚焦于信息缺口。
每轮提问后,总结已了解的信息并说明仍需确认的内容,再进行下一轮提问。当掌握足够信息可编写全面PRD时停止提问。
Generate .planning/specs/PRD.md
.planning/specs/PRD.md生成.planning/specs/PRD.md
.planning/specs/PRD.mdWrite a complete PRD with ALL sections:
markdown
undefined编写包含以下所有章节的完整PRD:
markdown
undefinedPRD: [Project Name]
PRD: [项目名称]
1. Overview
1. 项目概述
One paragraph: what this does and why.
一段文字说明:项目功能与价值。
2. Target Users
2. 目标用户
| User Type | Description | Primary Need |
|---|---|---|
| ... | ... | ... |
| 用户类型 | 描述 | 核心需求 |
|---|---|---|
| ... | ... | ... |
3. User Stories
3. 用户故事
Epic: [Feature Area 1]
史诗:[功能领域1]
- US-001: As a [user], I want to [action] so that [benefit]
- Acceptance Criteria:
- [Specific, testable criterion]
- [Specific, testable criterion]
- Acceptance Criteria:
(Continue for all epics/stories)
- US-001:作为[用户角色],我希望[执行操作],以便[获得收益]
- 验收标准:
- [具体、可测试的标准]
- [具体、可测试的标准]
- 验收标准:
(所有史诗/用户故事以此格式编写)
4. Technical Requirements
4. 技术需求
Stack
技术栈
| Layer | Technology | Rationale |
|---|---|---|
| ... | ... | ... |
| 层级 | 技术选型 | 选型理由 |
|---|---|---|
| ... | ... | ... |
Architecture
架构设计
- Key architectural decisions
- Data flow
- API structure
- 关键架构决策
- 数据流
- API结构
Data Model
数据模型
| Entity | Key Fields | Relationships |
|---|---|---|
| ... | ... | ... |
| 实体 | 核心字段 | 关系 |
|---|---|---|
| ... | ... | ... |
API Endpoints
API接口
| Method | Path | Purpose | Auth |
|---|---|---|---|
| ... | ... | ... | ... |
| 请求方法 | 路径 | 用途 | 认证方式 |
|---|---|---|---|
| ... | ... | ... | ... |
5. Screens & Navigation
5. 页面与导航
Screen Map
页面地图
(Tree diagram of all screens/routes)
(所有页面/路由的树形图)
Screen Descriptions
页面说明
| Screen | Purpose | Key Components |
|---|---|---|
| ... | ... | ... |
| 页面 | 用途 | 核心组件 |
|---|---|---|
| ... | ... | ... |
6. Non-Functional Requirements
6. 非功能性需求
- Performance targets
- Security requirements
- Accessibility
- Offline support
- 性能指标
- 安全要求
- 无障碍设计
- 离线支持
7. MVP Scope
7. MVP范围
In Scope (MVP)
包含内容(MVP)
Out of Scope (Post-MVP)
排除内容(Post-MVP)
8. Success Metrics
8. 成功指标
| Metric | Target | How Measured |
|---|---|---|
| ... | ... | ... |
| 指标 | 目标值 | 衡量方式 |
|---|---|---|
| ... | ... | ... |
9. Open Questions
9. 待确认问题
undefinedundefinedGet approval before proceeding
获得批准后再推进
Use AskUserQuestion: "PRD generated at . Ready to proceed, or want changes?"
.planning/specs/PRD.md使用AskUserQuestion:"PRD已生成于。是否可以继续推进,还是需要修改?"
.planning/specs/PRD.mdPHASE 2: GSD PROJECT BOOTSTRAP
阶段2:GSD项目初始化
Once the PRD is approved, create the full structure.
.planning/PRD获批后,创建完整的目录结构。
.planning/Step 1: Create directory structure
步骤1:创建目录结构
bash
mkdir -p .planning/specs .planning/codebase .planning/phasesbash
mkdir -p .planning/specs .planning/codebase .planning/phasesStep 2: Generate PROJECT.md (from PRD sections 1, 4, 7)
步骤2:生成PROJECT.md(基于PRD的第1、4、7章)
markdown
undefinedmarkdown
undefinedProject: [Name]
项目:[名称]
Vision
愿景
[From PRD §1 Overview]
[来自PRD §1 项目概述]
Requirements
需求
Validated
已确认
[From PRD §7 MVP In Scope — these are confirmed requirements]
[来自PRD §7 MVP包含内容——这些是已确认的需求]
Active (Under Discussion)
待讨论
[From PRD §9 Open Questions — unresolved items]
[来自PRD §9 待确认问题——未解决的事项]
Out of Scope
暂不考虑
[From PRD §7 Out of Scope]
[来自PRD §7 排除内容]
Constraints
约束条件
[From PRD §4 Stack rationale and §6 Non-Functional Requirements]
[来自PRD §4 技术栈选型理由与 §6 非功能性需求]
Key Decisions
关键决策
| Decision | Status | Rationale |
|---|---|---|
| [Stack choice from PRD §4] | Approved | [Rationale] |
| ... | ... | ... |
undefined| 决策内容 | 状态 | 理由 |
|---|---|---|
| [来自PRD §4的技术栈选择] | 已批准 | [选型理由] |
| ... | ... | ... |
undefinedStep 3: Generate ROADMAP.md (from PRD sections 3, 4, 5)
步骤3:生成ROADMAP.md(基于PRD的第3、4、5章)
Derive phases from the PRD. Every phase traces to user stories or technical requirements.
markdown
undefined从PRD中推导项目阶段。每个阶段都需关联到用户故事或技术需求。
markdown
undefinedRoadmap — Milestone 1: MVP
路线图 — 里程碑1:MVP
Progress
进度
| Phase | Name | Status | Plans |
|---|---|---|---|
| 1 | Infrastructure & Setup | Not Started | TBD |
| 2 | Auth & User Management | Not Started | TBD |
| 3 | [Core Feature 1] | Not Started | TBD |
| ... | ... | ... | ... |
| 阶段 | 名称 | 状态 | 计划 |
|---|---|---|---|
| 1 | 基础设施与初始化 | 未开始 | 待确定 |
| 2 | 认证与用户管理 | 未开始 | 待确定 |
| 3 | [核心功能1] | 未开始 | 待确定 |
| ... | ... | ... | ... |
Phase 1: Infrastructure & Setup
阶段1:基础设施与初始化
Goal: Project scaffolding, database schema, auth config, navigation skeleton
Depends on: None
Research: Likely
Research topics: [Stack from PRD §4]
Traces to: PRD §4 (Technical Requirements)
目标:项目脚手架搭建、数据库 schema 设计、认证配置、导航骨架开发
依赖:无
调研需求:是
调研主题:[来自PRD §4的技术栈]
关联PRD章节:PRD §4(技术需求)
Phase 2: Auth & User Management
阶段2:认证与用户管理
Goal: Sign up, login, forgot password, session management
Depends on: Phase 1
Research: Unlikely
Traces to: PRD §3 Epic: Auth, PRD §5 Auth Stack screens
目标:注册、登录、找回密码、会话管理
依赖:阶段1
调研需求:否
关联PRD章节:PRD §3 史诗:认证、PRD §5 认证页面
Phase 3: [Core Feature from PRD §3]
阶段3:[来自PRD §3的核心功能]
Goal: [From user story epic]
Depends on: Phase 1, Phase 2
Research: [Likely/Unlikely]
Traces to: PRD §3 Epic: [Name], US-001 through US-00N
(Continue for all phases derived from PRD)
目标:[来自用户故事史诗]
依赖:阶段1、阶段2
调研需求:[是/否]
关联PRD章节:PRD §3 史诗:[名称]、US-001至US-00N
(所有从PRD推导的阶段以此格式编写)
Phase N: Polish & Verification
阶段N:细节打磨与验证
Goal: Error states, empty states, performance, accessibility
Depends on: All previous phases
Traces to: PRD §6 Non-Functional Requirements
**Derivation rules:**
1. Infrastructure/setup is always Phase 1
2. Auth is Phase 2 (if applicable)
3. Each PRD Epic becomes one or more phases
4. PRD §5 Screen Map informs navigation phases
5. PRD §6 Non-Functional becomes a final polish phase
6. Every phase traces back to a PRD section目标:错误状态处理、空状态设计、性能优化、无障碍适配
依赖:所有前置阶段
关联PRD章节:PRD §6 非功能性需求
**阶段推导规则:**
1. 基础设施/初始化始终为阶段1
2. 认证功能为阶段2(若适用)
3. 每个PRD史诗对应一个或多个阶段
4. PRD §5 页面地图用于指导导航相关阶段
5. PRD §6 非功能性需求对应最终的细节打磨阶段
6. 每个阶段必须关联到PRD的具体章节Step 4: Generate STATE.md
步骤4:生成STATE.md
markdown
undefinedmarkdown
undefinedProject State
项目状态
Current Position
当前进度
- Phase: 1 of N (Infrastructure & Setup)
- Plan: Not started
- Status: Not started
- Progress: [░░░░░░░░░░] 0%
- 阶段:第1阶段/共N阶段(基础设施与初始化)
- 计划:未开始
- 状态:未开始
- 进度:[░░░░░░░░░░] 0%
Performance Metrics
性能指标
- Plans completed: 0
- Average duration: N/A
- Total execution time: 0
- 已完成计划数:0
- 平均耗时:无
- 总执行时间:0
Accumulated Context
累计上下文
- Decisions: See PROJECT.md
- Deferred issues: None
- Blockers: None
- 决策:详见PROJECT.md
- 延迟处理的问题:无
- 阻塞项:无
Session
会话
- Last activity: [date] — Project initialized
- Mode: Autonomous (Ralph loop)
undefined- 最后活动时间:[日期] — 项目初始化
- 模式:自主执行(Ralph循环)
undefinedStep 5: Generate config.json
步骤5:生成config.json
json
{
"mode": "yolo",
"depth": "comprehensive",
"gates": {
"confirm_project": false,
"confirm_phases": false,
"confirm_roadmap": false,
"confirm_breakdown": false,
"confirm_plan": false,
"execute_next_plan": true,
"issues_review": false,
"confirm_transition": false
},
"safety": {
"always_confirm_destructive": true,
"always_confirm_external_services": true
}
}Gates are set to for autonomous execution — Ralph doesn't stop to ask. Safety gates remain .
falsetruejson
{
"mode": "yolo",
"depth": "comprehensive",
"gates": {
"confirm_project": false,
"confirm_phases": false,
"confirm_roadmap": false,
"confirm_breakdown": false,
"confirm_plan": false,
"execute_next_plan": true,
"issues_review": false,
"confirm_transition": false
},
"safety": {
"always_confirm_destructive": true,
"always_confirm_external_services": true
}
}自主执行模式下,Gates设置为——Ralph不会中途停止询问。安全相关的Gates保持。
falsetrueStep 6: Generate codebase docs
步骤6:生成代码库文档
If the project directory already has code, run the equivalent of :
gsd:map-codebase- — technologies, deps, versions
.planning/codebase/STACK.md - — patterns, layers, data flow
.planning/codebase/ARCHITECTURE.md - — directory layout
.planning/codebase/STRUCTURE.md - — naming, style, patterns
.planning/codebase/CONVENTIONS.md
If it's a new project, create skeleton versions that get populated during Phase 1.
若项目目录已有代码,执行等效于的操作:
gsd:map-codebase- — 技术栈、依赖、版本
.planning/codebase/STACK.md - — 架构模式、层级、数据流
.planning/codebase/ARCHITECTURE.md - — 目录结构
.planning/codebase/STRUCTURE.md - — 命名规范、编码风格、设计模式
.planning/codebase/CONVENTIONS.md
若为新项目,则创建框架版本,在阶段1执行过程中逐步完善内容。
PHASE 3: PLAN GENERATION
阶段3:计划拆分
For Phase 1 only (the first phase to execute), generate full plans now. Subsequent phases get planned just-in-time by the loop, since earlier phases inform later decisions.
仅针对阶段1(首个执行阶段),现在生成完整计划。后续阶段的计划由循环实时生成,因为前期阶段的执行结果会影响后期决策。
For each plan in Phase 1, generate {NN}-{NN}-PLAN.md
:
{NN}-{NN}-PLAN.md为阶段1的每个计划生成{NN}-{NN}-PLAN.md
:
{NN}-{NN}-PLAN.mdxml
<plan>
<phase>1</phase>
<plan-number>01</plan-number>
<type>execute</type>
<name>[Descriptive name]</name>
</plan>
<objective>
[What this plan delivers and why, traced to PRD section]
</objective>
<context>
- PRD: .planning/specs/PRD.md
- Project: .planning/PROJECT.md
- Stack: .planning/codebase/STACK.md
</context>
<tasks>
<task type="auto">
<name>[Task name]</name>
<files>[Files to create/modify]</files>
<action>
[Detailed implementation instructions]
</action>
<verify>
- [ ] [Verification step]
- [ ] [Verification step]
</verify>
<done>[Success indicator]</done>
</task>
<!-- More tasks -->
</tasks>
<verification>
- [ ] All files created/modified as specified
- [ ] Tests pass
- [ ] No TypeScript/lint errors
- [ ] Acceptance criteria from PRD met
</verification>
<success_criteria>
[Definition of done for this plan]
</success_criteria>xml
<plan>
<phase>1</phase>
<plan-number>01</plan-number>
<type>execute</type>
<name>[描述性名称]</name>
</plan>
<objective>
[该计划的交付内容与价值,关联到PRD的具体章节]
</objective>
<context>
- PRD: .planning/specs/PRD.md
- 项目文档: .planning/PROJECT.md
- 技术栈: .planning/codebase/STACK.md
</context>
<tasks>
<task type="auto">
<name>[任务名称]</name>
<files>[需创建/修改的文件]</files>
<action>
[详细的实现说明]
</action>
<verify>
- [ ] [验证步骤]
- [ ] [验证步骤]
</verify>
<done>[成功标识]</done>
</task>
<!-- 更多任务 -->
</tasks>
<verification>
- [ ] 所有文件按要求创建/修改
- [ ] 测试通过
- [ ] 无TypeScript/代码检查错误
- [ ] 满足PRD中的验收标准
</verification>
<success_criteria>
[该计划的完成标准]
</success_criteria>PHASE 4: LOOP CONFIGURATION
阶段4:循环配置
Step 1: Check Ralph installation
步骤1:检查Ralph安装情况
bash
which ralph-loop 2>/dev/null || which ralph 2>/dev/nullIf not installed:
bash
git clone https://github.com/frankbria/ralph-claude-code.git /tmp/ralph-claude-code
cd /tmp/ralph-claude-code && ./install.shbash
which ralph-loop 2>/dev/null || which ralph 2>/dev/null若未安装:
bash
git clone https://github.com/frankbria/ralph-claude-code.git /tmp/ralph-claude-code
cd /tmp/ralph-claude-code && ./install.shStep 2: Generate .ralphrc
步骤2:生成.ralphrc
bash
PROJECT_NAME="$ARGUMENTS"
PROJECT_TYPE="[detected]"
MAX_CALLS_PER_HOUR=100
CLAUDE_TIMEOUT_MINUTES=20
CLAUDE_OUTPUT_FORMAT="json"
ALLOWED_TOOLS="Write,Read,Edit,Bash(git *),Bash(npm *),Bash(npx *),Skill(gsd:*)"
SESSION_CONTINUITY=true
SESSION_EXPIRY_HOURS=24
TASK_SOURCES="local"
CB_NO_PROGRESS_THRESHOLD=3
CB_SAME_ERROR_THRESHOLD=5
CB_OUTPUT_DECLINE_THRESHOLD=70Adjust per project type:
ALLOWED_TOOLS- TypeScript/Node:
Bash(npm *),Bash(npx *),Bash(node *) - Python:
Bash(python *),Bash(pip *),Bash(pytest *) - Rust:
Bash(cargo *),Bash(rustc *) - Go:
Bash(go *) - Add if Dockerfile present
Bash(docker *)
bash
PROJECT_NAME="$ARGUMENTS"
PROJECT_TYPE="[检测到的类型]"
MAX_CALLS_PER_HOUR=100
CLAUDE_TIMEOUT_MINUTES=20
CLAUDE_OUTPUT_FORMAT="json"
ALLOWED_TOOLS="Write,Read,Edit,Bash(git *),Bash(npm *),Bash(npx *),Skill(gsd:*)"
SESSION_CONTINUITY=true
SESSION_EXPIRY_HOURS=24
TASK_SOURCES="local"
CB_NO_PROGRESS_THRESHOLD=3
CB_SAME_ERROR_THRESHOLD=5
CB_OUTPUT_DECLINE_THRESHOLD=70根据项目类型调整:
ALLOWED_TOOLS- TypeScript/Node:
Bash(npm *),Bash(npx *),Bash(node *) - Python:
Bash(python *),Bash(pip *),Bash(pytest *) - Rust:
Bash(cargo *),Bash(rustc *) - Go:
Bash(go *) - 若存在Dockerfile,添加
Bash(docker *)
Step 3: Generate PROMPT.md
步骤3:生成PROMPT.md
This is the critical file — it tells the loop how to execute GSD plans with CoVe verification.
markdown
undefined这是核心配置文件——用于指导循环如何结合CoVe验证执行GSD计划。
markdown
undefinedProject: [PROJECT_NAME]
项目: [PROJECT_NAME]
Your Mission
你的任务
You are working autonomously in a Ralph loop executing GSD plans. You are equipped with wavybaby tools — use them. Each iteration:
你将在Ralph循环中自主执行GSD计划。已为你配备wavybaby工具——请务必使用。每次循环迭代:
0. Use your tools
0. 使用工具
You have been equipped with skills and MCP servers for this project. USE THEM:
- Context7: Query up-to-date docs before using any library. Don't guess APIs.
- Installed skills: Follow best practices from installed skill files.
- CoVe verification: For any non-trivial code (stateful, async, database, auth, security), run the 4-stage CoVe protocol from /rnv before committing.
已为当前项目配备技能与MCP服务器。请务必使用:
- Context7:使用任何库前先查询最新文档。切勿臆测API。
- 已安装的技能:遵循已安装技能文件中的最佳实践。
- CoVe验证:对于任何非trivial代码(有状态、异步、数据库、认证、安全相关),在提交前执行来自/rnv的四阶段CoVe验证流程。
1. Read current state
1. 读取当前状态
- Read to find current phase and plan
.planning/STATE.md - Read for phase context and dependencies
.planning/ROADMAP.md
- 读取以了解当前阶段与计划
.planning/STATE.md - 读取以获取阶段上下文与依赖关系
.planning/ROADMAP.md
2. Determine next action
2. 确定下一步操作
Follow this decision tree:
Is current phase's DISCOVERY.md missing?
YES → Run research: read PRD, explore codebase, write DISCOVERY.md
Use Context7 to look up docs for any unfamiliar tech.
NO ↓
Are there ungenerated plans for current phase?
YES → Generate next {NN}-{NN}-PLAN.md from DISCOVERY.md + PRD
NO ↓
Is there an unexecuted plan in current phase?
YES → Execute it (see "Execute a Plan" below)
NO ↓
Are all plans in current phase complete?
YES → Complete phase: update ROADMAP.md, advance STATE.md to next phase
NO → Something is wrong. Set STATUS: BLOCKED.
Are all phases complete?
YES → Run verification gate. If passing, set EXIT_SIGNAL: true
NO → Continue to next phase (loop back to top)遵循以下决策树:
当前阶段的DISCOVERY.md是否缺失?
是 → 执行调研:读取PRD、探索代码库、编写DISCOVERY.md
使用Context7查询任何不熟悉技术的文档。
否 ↓
当前阶段是否有未生成的计划?
是 → 根据DISCOVERY.md + PRD生成下一个{NN}-{NN}-PLAN.md
否 ↓
当前阶段是否有未执行的计划?
是 → 执行该计划(见下文“执行计划”)
否 ↓
当前阶段的所有计划是否已完成?
是 → 完成当前阶段:更新ROADMAP.md,将STATE.md推进到下一阶段
否 → 出现异常。设置状态为:阻塞。
所有阶段是否已完成?
是 → 执行最终验证。若通过,设置EXIT_SIGNAL: true
否 → 进入下一阶段(回到顶部循环)3. Execute a Plan
3. 执行计划
When executing a :
{NN}-{NN}-PLAN.md- Read the plan file completely
- Execute each in order
<task> - For non-trivial tasks, apply CoVe:
- Generate code [UNVERIFIED]
- Plan verification targets specific to THIS code
- Independently verify each target
- Apply fixes → [VERIFIED] code
- After each task, run its checks
<verify> - After all tasks, run the plan's section
<verification> - Write with results
{NN}-{NN}-SUMMARY.md - Commit changes with descriptive message
- Update (increment plan, update metrics)
.planning/STATE.md
执行时:
{NN}-{NN}-PLAN.md- 完整读取计划文件
- 按顺序执行每个
<task> - 对于非trivial任务,应用CoVe验证:
- 生成代码 [未验证]
- 针对该代码制定验证目标
- 独立验证每个目标
- 修复问题 → [已验证]代码
- 每个任务完成后,执行其检查
<verify> - 所有任务完成后,执行计划的部分
<verification> - 编写记录执行结果
{NN}-{NN}-SUMMARY.md - 提交变更并添加描述性提交信息
- 更新(推进计划进度,更新指标)
.planning/STATE.md
4. CoVe triggers
4. CoVe验证触发条件
Apply the full 4-stage CoVe protocol (from /rnv) for:
- Stateful code (useState, useReducer, context, stores)
- Async/concurrent logic (useEffect, mutations, subscriptions)
- Database operations (queries, transactions, migrations)
- Auth/security code
- Cache invalidation logic
- Financial or precision-critical calculations
- Any code where the bug would be subtle, not obvious
Skip CoVe only for: trivial one-liners, pure formatting, config files.
对以下代码应用完整的四阶段CoVe验证流程(来自/rnv):
- 有状态代码(useState、useReducer、context、状态管理库)
- 异步/并发逻辑(useEffect、数据变更、订阅)
- 数据库操作(查询、事务、迁移)
- 认证/安全相关代码
- 缓存失效逻辑
- 财务或精度敏感计算
- 任何bug难以察觉的代码
仅在以下情况跳过CoVe验证:琐碎的单行代码、纯格式调整、配置文件。
5. Generate plans for next phase (just-in-time)
5. 实时生成下一阶段计划
When advancing to a new phase:
- Read DISCOVERY.md for that phase (or create it first)
- Read relevant PRD sections (the phase's "Traces to" field)
- Use Context7 to look up any new tech introduced in this phase
- Generate all {NN}-{NN}-PLAN.md files for the phase
- Begin executing plan 01
进入新阶段时:
- 读取该阶段的DISCOVERY.md(若缺失则先创建)
- 读取相关PRD章节(阶段的“关联PRD章节”字段)
- 使用Context7查询该阶段引入的新技术文档
- 生成该阶段的所有{NN}-{NN}-PLAN.md文件
- 开始执行计划01
Key Rules
核心规则
- ONE plan per loop iteration (stay focused)
- Always run tests after implementation tasks
- Write SUMMARY.md after every completed plan
- Update STATE.md after every completed plan
- Reference the PRD for acceptance criteria — don't guess
- Use Context7 for library docs — don't hallucinate APIs
- Apply CoVe on non-trivial code — don't ship unverified
- If blocked, set STATUS: BLOCKED and explain why
- Never skip verification steps
- Commit atomically per task when possible
- 每次循环迭代仅执行一个计划(保持专注)
- 实现任务后始终运行测试
- 每个计划完成后编写SUMMARY.md
- 每个计划完成后更新STATE.md
- 参考PRD中的验收标准——切勿臆测
- 使用Context7查询库文档——避免API幻觉
- 对非trivial代码应用CoVe验证——不要交付未验证的代码
- 若陷入阻塞,设置状态为:阻塞并说明原因
- 切勿跳过验证步骤
- 尽可能按任务原子化提交变更
Required Output Format
输出格式要求
At the END of every response, output EXACTLY:
---RALPH_STATUS---
STATUS: IN_PROGRESS | COMPLETE | BLOCKED
PHASE: [current phase number and name]
PLAN: [current plan number or "generating" or "researching"]
TASKS_COMPLETED_THIS_LOOP: <number>
FILES_MODIFIED: <number>
TESTS_STATUS: PASSING | FAILING | NOT_RUN
WORK_TYPE: RESEARCH | PLANNING | IMPLEMENTATION | VERIFICATION
COVE_APPLIED: true | false | N/A
EXIT_SIGNAL: false
RECOMMENDATION: <what was done and what's next>
---END_RALPH_STATUS---
Set EXIT_SIGNAL: true ONLY when:
- ALL phases in ROADMAP.md are complete
- ALL SUMMARY.md files written
- Final verification gate passes
- STATE.md shows 100% progress
undefined每次响应的末尾,必须输出以下内容:
---RALPH_STATUS---
STATUS: IN_PROGRESS | COMPLETE | BLOCKED
PHASE: [当前阶段编号与名称]
PLAN: [当前计划编号或“生成中”或“调研中”]
TASKS_COMPLETED_THIS_LOOP: <数量>
FILES_MODIFIED: <数量>
TESTS_STATUS: PASSING | FAILING | NOT_RUN
WORK_TYPE: RESEARCH | PLANNING | IMPLEMENTATION | VERIFICATION
COVE_APPLIED: true | false | N/A
EXIT_SIGNAL: false
RECOMMENDATION: <已完成工作与下一步计划>
---END_RALPH_STATUS---
仅在以下情况设置EXIT_SIGNAL: true:
- ROADMAP.md中的所有阶段已完成
- 所有SUMMARY.md文件已编写
- 最终验证通过
- STATE.md显示进度100%
undefinedStep 4: Generate AGENT.md
步骤4:生成AGENT.md
markdown
undefinedmarkdown
undefinedAgent Instructions
Agent执行说明
Build
构建
[detected build command]
[检测到的构建命令]
Test
测试
[detected test command]
[检测到的测试命令]
Run
运行
[detected run command]
[检测到的启动命令]
Lint
代码检查
[detected lint command]
[检测到的代码检查命令]
Type Check
类型检查
[detected type check command if applicable]
[若适用,检测到的类型检查命令]
Equipped Tools
已配备工具
- Context7: Use then
mcp__plugin_context7_context7__resolve-library-idfor any library docsquery-docs - Installed skills: [list skills installed in Phase 0]
- CoVe: Apply 4-stage verification on non-trivial code (see PROMPT.md §4)
- Context7: 使用然后
mcp__plugin_context7_context7__resolve-library-id查询任何库的文档query-docs - 已安装技能: [阶段0中安装的技能列表]
- CoVe: 对非trivial代码应用四阶段验证(见PROMPT.md §4)
GSD Commands
GSD命令
- Execute plan: Read the PLAN.md and follow its tasks
- Write summary: Create SUMMARY.md after plan completion
- Update state: Modify STATE.md with progress
undefined- 执行计划: 读取PLAN.md并遵循其中的任务
- 编写总结: 计划完成后创建SUMMARY.md
- 更新状态: 修改STATE.md记录进度
undefinedStep 5: Add to .gitignore
步骤5:添加到.gitignore
bash
echo -e "\n# Ralph loop state\n.ralph/logs/\n.ralph/status.json\n.ralph/progress.json\n.ralph/.call_count\n.ralph/.last_reset\n.ralph/.exit_signals\n.ralph/.response_analysis\n.ralph/.circuit_breaker_state\n.ralph/.claude_session_id\n.ralph/.ralph_session\n.ralph/.ralph_session_history" >> .gitignorebash
echo -e "\n# Ralph循环状态\n.ralph/logs/\n.ralph/status.json\n.ralph/progress.json\n.ralph/.call_count\n.ralph/.last_reset\n.ralph/.exit_signals\n.ralph/.response_analysis\n.ralph/.circuit_breaker_state\n.ralph/.claude_session_id\n.ralph/.ralph_session\n.ralph/.ralph_session_history" >> .gitignoreStep 6: Print run instructions
步骤6:打印运行说明
Steve setup complete.
EQUIPPED:
Skills: [list installed skills]
MCP servers: [list configured servers]
Config: settings.local.json
PROJECT:
PRD: .planning/specs/PRD.md (review before running)
Project: .planning/PROJECT.md (derived from PRD)
Roadmap: .planning/ROADMAP.md (phases derived from PRD)
State: .planning/STATE.md (tracks progress)
Phase 1 Plans: .planning/phases/01-*/ (ready to execute)
LOOP:
Config: .ralphrc (rate limits, timeouts)
Prompt: .ralph/PROMPT.md (GSD + CoVe execution logic)
Build/test: .ralph/AGENT.md (edit if auto-detect wrong)
To run:
ralph --monitor # Recommended: loop + dashboard in tmux
ralph # Loop only
The loop will:
1. Execute Phase 1 plans sequentially (with CoVe on non-trivial code)
2. Write SUMMARY.md after each plan
3. Use Context7 for library docs (no hallucinated APIs)
4. Generate Phase 2 plans just-in-time
5. Continue through all phases
6. Run final verification gate
7. Exit when milestone is complete
To check progress:
cat .planning/STATE.md
ralph-monitorSteve配置完成。
已适配:
技能: [已安装技能列表]
MCP服务器: [已配置服务器列表]
配置文件: settings.local.json
项目文档:
PRD: .planning/specs/PRD.md (运行前请审阅)
项目概览: .planning/PROJECT.md (基于PRD生成)
路线图: .planning/ROADMAP.md (基于PRD推导的阶段)
状态跟踪: .planning/STATE.md (跟踪进度)
阶段1计划: .planning/phases/01-*/ (已准备好执行)
循环配置:
配置文件: .ralphrc (速率限制、超时设置)
执行提示: .ralph/PROMPT.md (GSD + CoVe执行逻辑)
构建/测试命令: .ralph/AGENT.md (若自动检测错误可编辑)
启动命令:
ralph --monitor # 推荐:循环执行 + tmux仪表盘
ralph # 仅循环执行
循环将:
1. 按顺序执行阶段1计划(非trivial代码经过CoVe验证)
2. 每个计划完成后编写SUMMARY.md
3. 使用Context7查询库文档(避免API幻觉)
4. 实时生成阶段2计划
5. 持续推进所有阶段
6. 执行最终验证
7. 里程碑完成后自动退出
查看进度:
cat .planning/STATE.md
ralph-monitorHOW THE LOOP EXECUTES GSD
循环执行GSD的流程
Per-Iteration Flow
单次迭代流程
Loop iteration N:
1. Read .planning/STATE.md
2. Identify: Phase X, Plan Y
3. If DISCOVERY.md missing → research phase (use Context7) → write DISCOVERY.md → done
4. If plans not generated → generate plans from DISCOVERY + PRD → done
5. Read .planning/phases/{X}-{name}/{XX}-{YY}-PLAN.md
6. Execute all tasks in plan
- Non-trivial code → CoVe 4-stage verification
- Library usage → Context7 doc lookup
7. Run verification checks
8. Write {XX}-{YY}-SUMMARY.md
9. Update STATE.md (plan Y+1, metrics)
10. If last plan in phase → update ROADMAP.md, advance to Phase X+1
11. If last phase → verification gate → EXIT_SIGNAL: true
12. Output RALPH_STATUS block第N次循环迭代:
1. 读取.planning/STATE.md
2. 确定:第X阶段,第Y计划
3. 若DISCOVERY.md缺失 → 执行阶段调研(使用Context7)→ 编写DISCOVERY.md → 完成本次迭代
4. 若计划未生成 → 根据DISCOVERY.md + PRD生成计划 → 完成本次迭代
5. 读取.planning/phases/{X}-{name}/{XX}-{YY}-PLAN.md
6. 执行计划中的所有任务
- 非trivial代码 → CoVe四阶段验证
- 使用库 → Context7文档查询
7. 执行验证检查
8. 编写{XX}-{YY}-SUMMARY.md
9. 更新STATE.md(推进到计划Y+1,更新指标)
10. 若为阶段最后一个计划 → 更新ROADMAP.md,推进到第X+1阶段
11. 若为最后一个阶段 → 执行最终验证 → 设置EXIT_SIGNAL: true
12. 输出RALPH_STATUS块Circuit Breaker (from Ralph)
断路器机制(来自Ralph)
| Trigger | Result |
|---|---|
| 3 loops no file changes | OPEN (halted) |
| 5 loops same error | OPEN (halted) |
| 2 loops no progress in STATE.md | HALF_OPEN (monitoring) |
| Progress resumes | CLOSED (recovered) |
| 触发条件 | 结果 |
|---|---|
| 3次循环无文件变更 | 开启(终止执行) |
| 5次循环出现相同错误 | 开启(终止执行) |
| 2次循环STATE.md无进度更新 | 半开启(监控状态) |
| 恢复进度 | 关闭(恢复执行) |
Exit Detection (Dual-Condition Gate)
退出检测(双条件验证)
Ralph only stops when BOTH:
- (from RALPH_STATUS blocks)
completion_indicators >= 2 - (all phases complete, verification gate passed)
EXIT_SIGNAL: true
仅当以下两个条件同时满足时,Ralph才会停止:
- (来自RALPH_STATUS块)
completion_indicators >= 2 - (所有阶段完成,最终验证通过)
EXIT_SIGNAL: true
Session Continuity
会话持久化
- Session persists via flag
--continue - provides additional continuity beyond Ralph's built-in session
.planning/STATE.md - Even if Ralph session resets, STATE.md tells the agent exactly where to resume
- 通过参数保持会话
--continue - 在Ralph内置会话之外提供额外的持久化支持
.planning/STATE.md - 即使Ralph会话重置,STATE.md也能告知Agent从何处继续执行
COMPARISON
对比
| Feature | Spidey | GSD only | Steve |
|---|---|---|---|
| Auto-equip (skills, MCP, config) | No | No | Yes (wavybaby) |
| PRD generation | Yes | No | Yes |
| Structured phases | No (flat checklist) | Yes | Yes |
| Discovery/research docs | No | Yes | Yes |
| Atomic plans with verification | No | Yes | Yes |
| CoVe code verification | No | No | Yes (wavybaby/rnv) |
| Context7 doc lookups | No | No | Yes (wavybaby) |
| State tracking | Basic | Detailed | Detailed |
| Autonomous execution | Yes (Ralph loop) | No (manual) | Yes (Ralph loop) |
| Circuit breakers | Yes | No | Yes |
| Session persistence | Ralph session | STATE.md | Both |
| Just-in-time planning | No (all upfront) | Yes | Yes |
| SUMMARY.md audit trail | No | Yes | Yes |
| Codebase documentation | No | Yes | Yes |
| Progress metrics/velocity | Basic | Detailed | Detailed |
Now setting up Steve for: $ARGUMENTS
| 特性 | Spidey | 仅GSD | Steve |
|---|---|---|---|
| 自动适配(技能、MCP、配置) | 否 | 否 | 是(wavybaby) |
| PRD生成 | 是 | 否 | 是 |
| 结构化阶段划分 | 否(扁平化 checklist) | 是 | 是 |
| 调研/需求文档 | 否 | 是 | 是 |
| 带验证的原子化计划 | 否 | 是 | 是 |
| CoVe代码验证 | 否 | 否 | 是(wavybaby/rnv) |
| Context7文档查询 | 否 | 否 | 是(wavybaby) |
| 状态跟踪 | 基础 | 详细 | 详细 |
| 自主执行 | 是(Ralph循环) | 否(手动) | 是(Ralph循环) |
| 断路器机制 | 是 | 否 | 是 |
| 会话持久化 | Ralph会话 | STATE.md | 两者兼具 |
| 实时计划生成 | 否(全部提前生成) | 是 | 是 |
| SUMMARY.md审计追踪 | 否 | 是 | 是 |
| 代码库文档 | 否 | 是 | 是 |
| 进度指标/执行速度 | 基础 | 详细 | 详细 |
正在为以下需求搭建Steve:$ARGUMENTS