ralphinho-rfc-pipeline
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseRalphinho 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无法一次性完成,必须拆分为多个可独立验证的工作单元时,可使用此技能。
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:
iddepends_onscopeacceptance_testsrisk_levelrollback_plan
每个工作单元应包含:
iddepends_onscopeacceptance_testsrisk_levelrollback_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
- Tier 1:独立文件编辑,确定性测试
- Tier 2:多文件行为变更,中等集成风险
- Tier 3:schema/auth/perf/security 相关变更
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.
- 永远不得合并存在未解决依赖失败的单元
- 始终基于最新集成分支对单元分支执行rebase操作
- 每次队列合并完成后重新运行集成测试
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 执行日志
- 单元评分卡
- 依赖图快照
- 集成风险汇总