lyxjack/ralphinho-rfc-pipeline
Tool/everything-claude-code/skills/ralphinho-rfc-pipeline/SKILL.md
RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
$ install --global
skillsauthnpx skillsauth add lyxjack/toolbox ralphinho-rfc-pipelineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 29, 2026, 8:05 AM36.5s1 file scanned
SKILL.md
- name:
- ralphinho-rfc-pipeline
- description:
- RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
- 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
- RFC intake
- DAG decomposition
- Unit assignment
- Unit implementation
- Unit validation
- Merge queue and integration
- Final system verification
Unit Spec Template
Each work unit should include:
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
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
Related Skills
lyxjack/unity-mcp-orchestrator
tools
VerifiedTrustedCommunity
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
1SKILL.mdUpdated Jun 11, 2026
lyxjack/test-driven-development
development
VerifiedTrustedCommunity
Use when implementing any feature or bugfix, before writing implementation code
1SKILL.mdUpdated Jun 11, 2026
lyxjack/systematic-debugging
development
VerifiedTrustedCommunity
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
1SKILL.mdUpdated Jun 11, 2026
lyxjack/writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment
1SKILL.mdUpdated Jun 11, 2026