Source profileQuality 68/100

affaan-m/ECC/skills/ralphinho-rfc-pipeline/SKILL.md

ralphinho-rfc-pipeline

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

Source repository stars
234,327
Declared platforms
0
Static risk flags
0
Last source update
2026-07-27
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/affaan-m/ECC --skill "skills/ralphinho-rfc-pipeline"
    Safe inspection promptEditorial

    Inspect the Agent Skill "ralphinho-rfc-pipeline" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/skills/ralphinho-rfc-pipeline/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      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

      RFC intakeDAG decompositionUnit assignment
    2. 02

      Unit Spec Template

      Each work unit should include: - id - dependson - scope - acceptancetests - risklevel - rollbackplan

      iddependsonscope
    3. 03

      Complexity Tiers

      Tier 1: isolated file edits, deterministic tests

      Tier 1: isolated file edits, deterministic testsTier 2: multi-file behavior changes, moderate integration riskTier 3: schema/auth/perf/security changes
    4. 04

      Quality Pipeline per Unit

      1. research 2. implementation plan 3. implementation 4. tests 5. review 6. merge-ready report

      researchimplementation planimplementation

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score68/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars234,327SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    affaan-m/ECC
    Skill path
    skills/ralphinho-rfc-pipeline/SKILL.md
    Commit
    4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    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

    Alternatives

    Compare before choosing

    Computed 67234,327

    affaan-m/ECC

    ralphinho-rfc-pipeline

    Review ralphinho-rfc-pipeline's use cases, installation, workflow, and original source instructions.

    2026-07-270 platforms
    Computed 57234,327

    affaan-m/ECC

    ralphinho-rfc-pipeline

    Review ralphinho-rfc-pipeline's use cases, installation, workflow, and original source instructions.

    2026-07-270 platforms