ralph-status

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Ralph Status Reporting

Ralph 状态报告

Overview

概述

The Ralph status block is a structured, machine-parseable progress report included at the end of every autonomous loop iteration. It enables automated monitoring, exit detection, and progress tracking. The format is rigid and must be followed exactly — machine parsing depends on consistent structure.
Announce at start: "Producing RALPH_STATUS block for this iteration."
Ralph状态块是一种结构化、机器可解析的进度报告,会附加在每一次自主循环迭代的末尾。它支持自动化监控、退出检测和进度跟踪。其格式要求严格,必须完全遵守——机器解析依赖于一致的结构。
开头声明: "Producing RALPH_STATUS block for this iteration."

Trigger Conditions

触发条件

  • End of every autonomous loop iteration (mandatory)
  • After BUILD phase completes in the autonomous loop
  • When monitoring systems need progress data
  • When exit gate evaluation is needed
  • When the
    autonomous-loop
    skill invokes this skill

  • 每一次自主循环迭代结束(强制要求)
  • 自主循环的BUILD阶段完成后
  • 监控系统需要进度数据时
  • 需要进行退出门限评估时
  • autonomous-loop
    技能调用本技能时

Phase 1: Data Collection

阶段1:数据收集

Goal: Gather all metrics needed for the status block.
  1. Count tasks completed in this iteration
  2. Count files modified (created, edited, deleted)
  3. Run the test suite and record result
  4. Determine the primary work type
  5. Check for blockers or issues
目标: 收集状态块所需的所有指标。
  1. 统计本次迭代完成的任务数
  2. 统计修改的文件数(创建、编辑、删除)
  3. 运行测试套件并记录结果
  4. 确定核心工作类型
  5. 检查是否存在阻塞项或问题

Metric Collection Table

指标收集表

MetricHow to DetermineExample
TASKS_COMPLETED_THIS_LOOPCount tasks marked complete this iteration1
FILES_MODIFIEDCount files changed via git diff or tracking3
TESTS_STATUSRun test suite, record overall resultPASSING
WORK_TYPECategorize the primary activityIMPLEMENTATION
BlockersCheck if any task was unable to proceedNone
Metric判定方式示例
TASKS_COMPLETED_THIS_LOOP统计本次迭代中标记为完成的任务数1
FILES_MODIFIED通过git diff或追踪工具统计变更的文件数3
TESTS_STATUS运行测试套件,记录整体结果PASSING
WORK_TYPE对核心活动进行分类IMPLEMENTATION
Blockers检查是否有任务无法推进None

Work Type Classification

工作类型分类

Work TypeWhen to Use
IMPLEMENTATIONNew code written (features, endpoints, services)
TESTINGPrimary activity was writing or fixing tests
DOCUMENTATIONPrimary activity was docs, specs, or comments
REFACTORINGPrimary activity was restructuring without behavior change
STOP — Do NOT proceed to Phase 2 until:
  • All metrics are collected
  • Test suite has been run (not assumed)
  • Work type is determined

工作类型适用场景
IMPLEMENTATION编写新代码(功能、接口、服务)
TESTING核心活动为编写或修复测试用例
DOCUMENTATION核心活动为编写文档、规范或注释
REFACTORING核心活动为代码结构重构,不改变功能逻辑
停止 — 满足以下条件前请勿进入阶段2:
  • 所有指标已收集完成
  • 已实际运行测试套件(不得假设结果)
  • 已确定工作类型

Phase 2: STATUS Evaluation

阶段2:STATUS 评估

Goal: Determine the correct STATUS value based on iteration outcome.
目标: 根据迭代结果确定正确的STATUS值。

STATUS Decision Table

STATUS 决策表

ConditionSTATUS ValueEXIT_SIGNAL
Tasks remain, work completed this iterationIN_PROGRESSfalse
Tasks remain, no work completed (investigation)IN_PROGRESSfalse
Cannot proceed, needs external inputBLOCKEDfalse
All tasks complete, all tests passCOMPLETEEvaluate Phase 3
All tasks complete, tests failingIN_PROGRESSfalse
条件STATUS 值EXIT_SIGNAL
仍有未完成任务,本次迭代有产出IN_PROGRESSfalse
仍有未完成任务,本次迭代无产出(仅调研)IN_PROGRESSfalse
无法推进,需要外部输入BLOCKEDfalse
所有任务完成,所有测试通过COMPLETE进入阶段3评估
所有任务完成,测试未通过IN_PROGRESSfalse

STATUS Values Defined

STATUS 值定义

ValueMeaningLoop Action
IN_PROGRESSWork is ongoing, tasks remain or tests failingContinue loop
COMPLETEAll planned work is finished, tests passEvaluate exit gate
BLOCKEDCannot proceed without external inputHalt and report
含义循环动作
IN_PROGRESS工作仍在进行,有未完成任务或测试未通过继续循环
COMPLETE所有计划工作已完成,测试通过评估退出门限
BLOCKED无外部输入则无法推进暂停并上报

When BLOCKED

处于 BLOCKED 状态时

  1. Clearly describe what is blocking progress in RECOMMENDATION
  2. Set
    EXIT_SIGNAL: false
    (blocked is not complete)
  3. The circuit breaker may activate if blocked state persists across iterations
STOP — Do NOT proceed to Phase 3 until:
  • STATUS value is determined
  • If BLOCKED, blocker is clearly described

  1. 在RECOMMENDATION中清晰描述阻塞进度的原因
  2. 设置
    EXIT_SIGNAL: false
    (阻塞不等于完成)
  3. 如果多次迭代都处于阻塞状态,熔断器可能会触发
停止 — 满足以下条件前请勿进入阶段3:
  • 已确定STATUS值
  • 如果为BLOCKED状态,已清晰描述阻塞原因

Phase 3: EXIT_SIGNAL Evaluation

阶段3:EXIT_SIGNAL 评估

Goal: Determine whether EXIT_SIGNAL should be true or false.
<HARD-GATE> EXIT_SIGNAL may ONLY be `true` when ALL of these conditions are simultaneously met: </HARD-GATE>
ConditionHow to VerifyRequired
No remaining tasksIMPLEMENTATION_PLAN.md has no unchecked itemsYes
All tests passTESTS_STATUS is PASSINGYes
No errors in latest iterationClean execution, no unresolved exceptionsYes
No meaningful work remainsNo TODOs, no incomplete features, code review doneYes
目标: 确定EXIT_SIGNAL应该为true还是false。
<HARD-GATE> EXIT_SIGNAL仅当所有以下条件同时满足时才可以设为`true`: </HARD-GATE>
条件校验方式是否必填
无剩余任务IMPLEMENTATION_PLAN.md中没有未勾选的项
所有测试通过TESTS_STATUS为PASSING
本次迭代无错误执行过程干净,无未解决的异常
无剩余有效工作无TODO项、无未完成功能、代码评审已完成

EXIT_SIGNAL Decision Table

EXIT_SIGNAL 决策表

Tasks RemainingTests StatusErrorsMeaningful WorkEXIT_SIGNAL
YesAnyAnyAnyfalse
NoFAILINGAnyAnyfalse
NoPASSINGYesAnyfalse
NoPASSINGNoYesfalse
NoPASSINGNoNotrue
剩余任务测试状态错误剩余有效工作EXIT_SIGNAL
任意任意任意false
FAILING任意任意false
PASSING任意false
PASSINGfalse
PASSINGtrue

Dual-Condition Exit Gate

双条件退出门限

The loop orchestrator uses TWO independent signals to confirm exit:
  1. Heuristic detection: Completion language ("all done", "everything passes", "no remaining work") appears >= 2 times in recent output
  2. Explicit declaration:
    EXIT_SIGNAL: true
    in the status block
Both must be true simultaneously. This prevents:
  • False positives from casual completion language
  • Premature exits when Claude says "done" while still working productively
STOP — Do NOT set EXIT_SIGNAL to true unless ALL four conditions are verified.

循环编排器需要两个独立信号同时满足才能确认退出:
  1. 启发式检测: 最近输出中出现完成类表述("all done"、"everything passes"、"no remaining work")的次数≥2次
  2. 显式声明: 状态块中
    EXIT_SIGNAL: true
两个条件必须同时满足,避免以下问题:
  • 随意的完成表述导致的误判
  • 当Claude表示“已完成”但实际仍在有效工作时的提前退出
停止 — 除非所有四个条件都已校验通过,否则请勿将EXIT_SIGNAL设为true。

Phase 4: Block Production

阶段4:块生成

Goal: Write the RALPH_STATUS block in exact format.
<HARD-GATE> Every loop iteration MUST end with this exact format. No variations. No additional fields. No missing fields. </HARD-GATE>
目标: 严格按照格式编写RALPH_STATUS块。
<HARD-GATE> 每一次循环迭代必须严格遵循该格式结束。不得有任何变动、不得添加额外字段、不得缺失字段。 </HARD-GATE>

Required Format

要求格式

---RALPH_STATUS---
STATUS: [IN_PROGRESS | COMPLETE | BLOCKED]
TASKS_COMPLETED_THIS_LOOP: [number]
FILES_MODIFIED: [number]
TESTS_STATUS: [PASSING | FAILING | NOT_RUN]
WORK_TYPE: [IMPLEMENTATION | TESTING | DOCUMENTATION | REFACTORING]
EXIT_SIGNAL: [false | true]
RECOMMENDATION: [one-line summary of next action or completion state]
---END_RALPH_STATUS---
---RALPH_STATUS---
STATUS: [IN_PROGRESS | COMPLETE | BLOCKED]
TASKS_COMPLETED_THIS_LOOP: [number]
FILES_MODIFIED: [number]
TESTS_STATUS: [PASSING | FAILING | NOT_RUN]
WORK_TYPE: [IMPLEMENTATION | TESTING | DOCUMENTATION | REFACTORING]
EXIT_SIGNAL: [false | true]
RECOMMENDATION: [one-line summary of next action or completion state]
---END_RALPH_STATUS---

Field Specifications

字段规范

FieldTypeAllowed ValuesDescription
STATUSenumIN_PROGRESS, COMPLETE, BLOCKEDCurrent iteration outcome
TASKS_COMPLETED_THIS_LOOPinteger0+Number of tasks finished this iteration
FILES_MODIFIEDinteger0+Number of files changed (created, edited, deleted)
TESTS_STATUSenumPASSING, FAILING, NOT_RUNState of test suite after this iteration
WORK_TYPEenumIMPLEMENTATION, TESTING, DOCUMENTATION, REFACTORINGPrimary activity category
EXIT_SIGNALbooleanfalse, trueWhether all work is complete
RECOMMENDATIONstringFree text (one line only)Next action or final summary
字段类型允许值描述
STATUS枚举IN_PROGRESS, COMPLETE, BLOCKED当前迭代的结果
TASKS_COMPLETED_THIS_LOOP整数0及以上本次迭代完成的任务数量
FILES_MODIFIED整数0及以上变更的文件数量(创建、编辑、删除)
TESTS_STATUS枚举PASSING, FAILING, NOT_RUN本次迭代后测试套件的状态
WORK_TYPE枚举IMPLEMENTATION, TESTING, DOCUMENTATION, REFACTORING核心活动分类
EXIT_SIGNAL布尔值false, true是否所有工作都已完成
RECOMMENDATION字符串自由文本(仅一行)下一步动作或最终总结

RECOMMENDATION Guidelines

RECOMMENDATION 编写指南

STATUSRECOMMENDATION Content
IN_PROGRESS"Next: [specific next task]"
COMPLETE"All tasks complete, tests passing, [summary]"
BLOCKED"Blocked: [specific blocker description]"

STATUSRECOMMENDATION 内容
IN_PROGRESS"Next: [具体的下一个任务]"
COMPLETE"All tasks complete, tests passing, [总结内容]"
BLOCKED"Blocked: [具体的阻塞原因描述]"

Phase 5: Validation

阶段5:校验

Goal: Verify the status block is correct before output.
目标: 在输出前验证状态块是否正确。

Validation Checks

校验项

CheckRuleIf Violated
Format exactMatches template character-for-character (except values)Rewrite block
STATUS consistencyCOMPLETE requires EXIT_SIGNAL evaluationFix STATUS or EXIT_SIGNAL
TESTS_STATUS matches realityValue matches actual test run resultRe-run tests
EXIT_SIGNAL justifiedtrue only when all 4 conditions metSet to false
RECOMMENDATION presentNon-empty, one lineAdd recommendation
No extra fieldsOnly the 7 defined fieldsRemove extras

检查项规则违反后处理
格式完全匹配除了填充值外,逐字符匹配模板重写状态块
STATUS 一致性COMPLETE状态必须完成EXIT_SIGNAL评估修复STATUS或EXIT_SIGNAL
TESTS_STATUS 符合实际值与实际测试运行结果一致重新运行测试
EXIT_SIGNAL 合理仅当所有4个条件满足时才能为true设为false
RECOMMENDATION 存在非空,仅一行补充推荐内容
无额外字段仅包含定义的7个字段删除额外字段

Anti-Patterns / Common Mistakes

反模式/常见错误

Anti-PatternWhy It FailsCorrect Approach
Omitting the status blockLoop cannot evaluate exit, monitoring blindEvery iteration ends with status
Setting EXIT_SIGNAL true with failing testsPremature exit, broken codeVerify all 4 conditions
Adding custom fieldsMachine parsing breaksOnly the 7 defined fields
Multi-line RECOMMENDATIONParsing breaks on newlinesOne line only
TESTS_STATUS without running testsFalse confidenceActually run the test suite
STATUS: COMPLETE with tasks remainingContradictory signalCheck IMPLEMENTATION_PLAN.md
Skipping RECOMMENDATIONNo guidance for next iterationAlways include actionable recommendation
EXIT_SIGNAL: true when BLOCKEDContradictory — blocked is not completeBLOCKED always has EXIT_SIGNAL: false
Changing the;
Machine parsing depends on exact delimitersUse ---RALPH_STATUS--- exactly
Guessing FILES_MODIFIEDInaccurate metricsCount actual changes

反模式错误原因正确做法
遗漏状态块循环无法评估退出条件,监控失效每次迭代末尾必须输出状态块
测试未通过时设置EXIT_SIGNAL为true提前退出,提交有问题的代码校验所有4个条件
添加自定义字段破坏机器解析仅使用定义的7个字段,额外信息放在RECOMMENDATION
多行RECOMMENDATION换行导致解析失败仅写一行
未运行测试就填写TESTS_STATUS带来错误的信心实际运行测试套件后再填写
仍有剩余任务时设置STATUS: COMPLETE信号矛盾检查IMPLEMENTATION_PLAN.md
跳过RECOMMENDATION下一次迭代没有指导始终包含可执行的推荐内容
BLOCKED状态时设置EXIT_SIGNAL: true逻辑矛盾——阻塞不等于完成BLOCKED状态的EXIT_SIGNAL永远为false
修改分隔符格式机器解析依赖精确的分隔符严格使用---RALPH_STATUS---格式
估算FILES_MODIFIED数值指标不准确统计实际变更的文件数

Anti-Rationalization Guards

反合理化防护

<HARD-GATE> Do NOT skip the status block. Do NOT set EXIT_SIGNAL to true unless all four conditions are verified. Do NOT modify the block; . Machine parsing depends on exact, consistent structure. </HARD-GATE>
If you catch yourself thinking:
  • "The status block is just overhead..." — It is the exit gate mechanism. Never skip.
  • "Everything is done, EXIT_SIGNAL: true..." — Verify ALL four conditions first.
  • "I'll add an extra field for more detail..." — No. Use RECOMMENDATION for details.
  • "Tests probably pass, TESTS_STATUS: PASSING..." — Run them. Verify. Then report.

<HARD-GATE> 不得跳过状态块生成。除非所有四个条件都校验通过,否则不得将EXIT_SIGNAL设为true。不得修改块格式。机器解析依赖于精确、一致的结构。 </HARD-GATE>
如果你出现以下想法:
  • "状态块只是多余的开销..." —— 它是退出门限机制,永远不能跳过。
  • "所有工作都做完了,直接设EXIT_SIGNAL: true..." —— 先校验所有四个条件。
  • "我加个额外字段说明更多细节..." —— 不行,额外信息放在RECOMMENDATION里。
  • "测试应该能过,直接填TESTS_STATUS: PASSING..." —— 实际运行,校验后再上报。

Integration Points

集成点

SkillRelationshipWhen
autonomous-loop
Parent — invokes this skill at end of each iterationEvery iteration
circuit-breaker
Consumer — monitors for stagnation patternsReads status blocks
verification-before-completion
Upstream — provides test resultsBefore status block production
Monitoring dashboardConsumer — displays real-time progressReads status blocks
Log aggregationConsumer — historical performance analysisStores status blocks

技能关系触发时机
autonomous-loop
父技能——每次迭代结束时调用本技能每次迭代
circuit-breaker
消费者——监控停滞模式读取状态块
verification-before-completion
上游依赖——提供测试结果生成状态块之前
监控面板消费者——展示实时进度读取状态块
日志聚合系统消费者——历史性能分析存储状态块

Concrete Examples

具体示例

Example: Typical IN_PROGRESS Status

示例:典型的IN_PROGRESS状态

---RALPH_STATUS---
STATUS: IN_PROGRESS
TASKS_COMPLETED_THIS_LOOP: 1
FILES_MODIFIED: 3
TESTS_STATUS: PASSING
WORK_TYPE: IMPLEMENTATION
EXIT_SIGNAL: false
RECOMMENDATION: Next: implement user authentication middleware
---END_RALPH_STATUS---
---RALPH_STATUS---
STATUS: IN_PROGRESS
TASKS_COMPLETED_THIS_LOOP: 1
FILES_MODIFIED: 3
TESTS_STATUS: PASSING
WORK_TYPE: IMPLEMENTATION
EXIT_SIGNAL: false
RECOMMENDATION: Next: implement user authentication middleware
---END_RALPH_STATUS---

Example: Completion Status

示例:完成状态

---RALPH_STATUS---
STATUS: COMPLETE
TASKS_COMPLETED_THIS_LOOP: 1
FILES_MODIFIED: 2
TESTS_STATUS: PASSING
WORK_TYPE: DOCUMENTATION
EXIT_SIGNAL: true
RECOMMENDATION: All tasks complete, tests passing, documentation updated
---END_RALPH_STATUS---
---RALPH_STATUS---
STATUS: COMPLETE
TASKS_COMPLETED_THIS_LOOP: 1
FILES_MODIFIED: 2
TESTS_STATUS: PASSING
WORK_TYPE: DOCUMENTATION
EXIT_SIGNAL: true
RECOMMENDATION: All tasks complete, tests passing, documentation updated
---END_RALPH_STATUS---

Example: Blocked Status

示例:阻塞状态

---RALPH_STATUS---
STATUS: BLOCKED
TASKS_COMPLETED_THIS_LOOP: 0
FILES_MODIFIED: 0
TESTS_STATUS: PASSING
WORK_TYPE: IMPLEMENTATION
EXIT_SIGNAL: false
RECOMMENDATION: Blocked: need database credentials for integration test setup
---END_RALPH_STATUS---
---RALPH_STATUS---
STATUS: BLOCKED
TASKS_COMPLETED_THIS_LOOP: 0
FILES_MODIFIED: 0
TESTS_STATUS: PASSING
WORK_TYPE: IMPLEMENTATION
EXIT_SIGNAL: false
RECOMMENDATION: Blocked: need database credentials for integration test setup
---END_RALPH_STATUS---

Example: Test Failure Status

示例:测试失败状态

---RALPH_STATUS---
STATUS: IN_PROGRESS
TASKS_COMPLETED_THIS_LOOP: 1
FILES_MODIFIED: 4
TESTS_STATUS: FAILING
WORK_TYPE: TESTING
EXIT_SIGNAL: false
RECOMMENDATION: 3 tests failing in auth module — investigating root cause next iteration
---END_RALPH_STATUS---

---RALPH_STATUS---
STATUS: IN_PROGRESS
TASKS_COMPLETED_THIS_LOOP: 1
FILES_MODIFIED: 4
TESTS_STATUS: FAILING
WORK_TYPE: TESTING
EXIT_SIGNAL: false
RECOMMENDATION: 3 tests failing in auth module — investigating root cause next iteration
---END_RALPH_STATUS---

Process Summary

流程总结

  1. Complete the iteration's work (implementation, testing, docs, or refactoring)
  2. Count tasks completed and files modified
  3. Run the test suite and record result
  4. Evaluate STATUS value
  5. Evaluate EXIT_SIGNAL conditions (all 4 must be true for
    true
    )
  6. Write the RALPH_STATUS block in exact format
  7. Include a clear, actionable RECOMMENDATION

  1. 完成本次迭代的工作(编码、测试、文档或重构)
  2. 统计完成的任务数和修改的文件数
  3. 运行测试套件并记录结果
  4. 评估STATUS值
  5. 评估EXIT_SIGNAL条件(4个条件全部满足才能设为
    true
  6. 严格按照格式编写RALPH_STATUS块
  7. 包含清晰、可执行的RECOMMENDATION

Skill Type

技能类型

RIGID — The status block format must be followed exactly. Machine parsing depends on consistent structure. No field additions, no format changes, no skipped blocks.
RIGID — 必须严格遵守状态块格式。机器解析依赖于一致的结构。不得新增字段、不得修改格式、不得跳过块生成。