← Browse

@loulanyue/ralphinho-rfc-pipeline

A

RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.

skillclaude

Install

agr install @loulanyue/ralphinho-rfc-pipeline --target claude

Writes 1 file into .claude/skills/, pinned to git-639e9a5f.

  • .claude/skills/ralphinho-rfc-pipeline/SKILL.md

Document


name: ralphinho-rfc-pipeline description: RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration. source_path: skills/ralphinho-rfc-pipeline/SKILL.md origin: ECC

Ralphinho RFC Pipeline

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.

Pipeline Stages

  1. RFC intake
  2. DAG decomposition
  3. Unit assignment
  4. Unit implementation
  5. Unit validation
  6. Merge queue and integration
  7. Final system verification

Unit Spec Template

Each work unit should include:

  • 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

Quality Pipeline per Unit

  1. research
  2. implementation plan
  3. implementation
  4. tests
  5. review
  6. 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

原文

導航

Repository README

Describes loulanyue/awesome-claude-notes as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.

awesome claude notes

语言

Stars Forks Contributors npm ecc-universal npm ecc-agentshield GitHub App Install License

一套面向 Claude Code 与多种 AI coding harness 的生产级工作流资产库。

把 AI coding agent 从“偶尔好用”,推进到“稳定可复用”。

awesome claude notes 提供已经打磨过的 agents、skills、commands、rules、hooks、 MCP configs 和跨平台脚本,帮助你更快搭起一套可落地的 agent harness,而不是从零 拼装目录、提示词和自动化流程。

[!IMPORTANT] 本仓库是基于 affaan-m/ECC 的独立社区发行版, 重点维护中文文档、打包与跨工具使用体验,并非官方上游。原作者、贡献者和 MIT 许可证信息均予以保留;同步与差异策略见 UPSTREAM.md

为什么会用它

你通常会在下面这些场景里需要这个仓库:

  • 你想快速得到一套能直接落地的 Claude Code 工作流。
  • 你需要的不只是提示词,而是一整套 agents、rules、hooks 和 commands。
  • 你希望同一套方法可以覆盖 Claude Code、Cursor、Codex、OpenCode 等工具。

你会得到什么

  • 更快开始:直接复用现成的目录结构、命令和默认约束。
  • 更稳的工作流:把常见的开发、评审、测试和安全检查沉淀成可重复流程。
  • 更少重复搭建:不用自己从头整理 agents、skills、rules、hooks 和 MCP 配置。
  • 更好的跨工具迁移:同一套资产可复用到多个 agent / IDE / CLI 组合中。

说明:当前仓库默认以中文作为根 README 展示,README.zh-CN.md 为同步镜像;旧资料里出现的历史仓库名通常只是旧截图或旧安装残留。

2 分钟开始

推荐路径只保留一条:先安装插件,再安装你当前语言需要的规则和命令。

Quick start gives you access to 28 agents, 125 skills, and 60 commands.

1. 安装插件

/plugin marketplace add loulanyue/awesome-claude-notes
/plugin install awesome-claude-notes@awesome-claude-notes

2. 安装语言资产

Claude Code 插件不会自动分发 rules,所以这一步仍然必需。

git clone https://github.com/loulanyue/awesome-claude-notes.git
cd awesome-claude-notes
npm install
npx ecc typescript

可替换语言示例:pythongolangswiftphp。 兼容旧入口:npx ecc-install typescript

3. 直接开始用

/awesome-claude-notes:plan "Add user authentication"

如果你是手动安装命令,也可以直接使用: /plan "Add user authentication"

接下来该看哪份文档

仓库里包含什么

这个仓库的核心目录与能力如下:

CategorySnapshotNotes
Agents✅ 28 agentsSpecialized subagents for planning, review, build fixing, and orchestration
Commands✅ 60 commandsSlash-command workflows for planning, testing, review, and maintenance
Skills✅ 125 skillsReusable workflow and domain-knowledge modules across harnesses
  • agents/:专用子代理,例如 planner、architect、code-reviewer、build resolver。
  • skills/:工作流定义与领域知识模块。
  • commands/:可直接调用的 slash commands,如 /plan/tdd/code-review
  • hooks/:基于工具和生命周期事件的自动化。
  • rules/:始终生效的公共规则与语言专属规则。
  • mcp-configs/:外部集成所需的 MCP 配置。
  • scripts/:跨平台 Node.js 安装与运维脚本。
  • tests/:脚本与安装器的验证用例。

package.json 当前发布内容看,仓库同时覆盖 Claude、Cursor、Codex、 OpenCode 相关资产,以及 ecc / ecc-install 两个 CLI 入口。

平台支持摘要

  • Claude Code:推荐主路径,插件、commands、hooks、rules 支持最完整。
  • Cursor:提供适配后的 rules、skills、commands 与相关配置。
  • Codex:提供 .codex/AGENTS.md 体系,约束能力更依赖说明文件和沙箱配置。
  • OpenCode:提供对应 commands、instructions、plugins 与工具层适配。
  • 操作系统:脚本基于 Node.js,面向 macOS、Linux、Windows。

精简 FAQ

为什么安装插件后还要执行 npx ecc <language>

因为 Claude Code 插件本身不能自动分发 rules。 推荐保留插件安装,再用 npx ecc <language> 安装当前语言所需资产。

可以只装一部分吗?

可以。选择性安装入口保留为: npx ecc install --profile ...npx ecc install --modules ...。 详细说明见 docs/SELECTIVE-INSTALL-ARCHITECTURE.md

可以完全手动安装吗?

可以。如果你希望自己管理 ~/.claude/agents/~/.claude/rules/~/.claude/commands/~/.claude/skills/,请参考完整说明: docs/zh-CN/README.md

遇到 Duplicate hooks file 怎么办?

最常见原因是在 .claude-plugin/plugin.json 里手动声明了 "hooks" 字段。 Claude Code v2.1+ 会自动加载插件中的 hooks/hooks.json,删除重复声明即可。

需要什么环境?

Node.js 版本要求见 package.json>=18)。 文档校验入口为 npm run lint,完整校验可运行 npm test

贡献与许可

MIT。欢迎按现有目录约定贡献新的 agents、skills、commands、hooks、rules、 文档和翻译。


⭐ Star History

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-639e9a5fc3d22026-07-31