Back to Details

ralphinho-rfc-pipeline

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Ralphinho RFC Pipeline

Ralphinho RFC 流水线

Inspired by humanplane style RFC decomposition patterns and multi-unit orchestration workflows.

Use this skill when a feature is too large for a single agent pass and must be split into independently verifiable work units.

灵感来源于humanplane风格的RFC分解模式和多单元编排工作流。

当某个功能过于庞大，无法由单个Agent一次性处理，且必须拆分为可独立验证的工作单元时，可使用本Skill。

Pipeline Stages

流水线阶段

RFC intake
DAG decomposition
Unit assignment
Unit implementation
Unit validation
Merge queue and integration
Final system verification

RFC接收
DAG分解
单元分配
单元实现
单元验证
合并队列与集成
最终系统验证

Unit Spec Template

工作单元规范模板

Each work unit should include:

```
id
```
```
depends_on
```
```
scope
```
```
acceptance_tests
```
```
risk_level
```
```
rollback_plan
```

每个工作单元应包含：

```
id
```
（单元ID）
```
depends_on
```
（依赖项）
```
scope
```
（范围）
```
acceptance_tests
```
（验收测试）
```
risk_level
```
（风险等级）
```
rollback_plan
```
（回滚计划）

Complexity Tiers

复杂度层级

Tier 1: isolated file edits, deterministic tests
Tier 2: multi-file behavior changes, moderate integration risk
Tier 3: schema/auth/perf/security changes

层级1：独立文件编辑，确定性测试
层级2：多文件行为变更，中等集成风险
层级3：Schema/权限/性能/安全变更

Quality Pipeline per Unit

每个单元的质量流水线

research
implementation plan
implementation
tests
review
merge-ready report

调研
实现计划
实现
测试
评审
可合并报告

Merge Queue Rules

合并队列规则

Never merge a unit with unresolved dependency failures.
Always rebase unit branches on latest integration branch.
Re-run integration tests after each queued merge.

绝不合并存在未解决依赖失败的单元。
始终将单元分支变基到最新的集成分支。
每次队列合并后重新运行集成测试。

Recovery

恢复机制

If a unit stalls:

evict from active queue
snapshot findings
regenerate narrowed unit scope
retry with updated constraints

如果某个单元停滞：

从活动队列中移除
保存当前结果快照
重新生成缩小范围的单元
使用更新后的约束条件重试

Outputs

输出内容

RFC execution log
unit scorecards
dependency graph snapshot
integration risk summary

RFC执行日志
单元评分卡
依赖关系图快照
集成风险摘要