change-forge-router

Route ambiguous product change requests to minimum sufficient ChangeForge skill paths.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/machenjie/rd-skills --skill change-forge-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-forge-router
Source: https://github.com/machenjie/rd-skills/tree/main/src/professional-skills/change-forge-router
Command: npx skills add https://github.com/machenjie/rd-skills --skill change-forge-router

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It resolves ambiguous or broad change requests into a safe, minimum-sufficient ChangeForge execution path by classifying change type, risk, impacted areas, required quality gates, and the right professional/domain capabilities.

Core Features & Use Cases

  • Central change classification and routing: Determines the smallest professional skill sequence needed to address the request without over-routing or assuming missing evidence.
  • Risk and evidence-aware orchestration: Escalates risk for security/privacy, data integrity, external integrations, migrations, production deployment, irreversibility, and rollback uncertainty.
  • Foundation-to-professional capability binding: Selects only the necessary foundation capabilities required by the chosen professional skills.
  • Domain extension gating: Attaches Web3/AI/mobile/bigdata/payment/IoT/low-level extensions only when clear domain signals exist.
  • Structured, handoff-ready output: Produces a detailed routing result with task DAG, required references, and quality gates to enable immediate next-step execution.

Quick Start

Use the router when a request does not already specify a complete skill path, risk level, impact model, runtime profile awareness, and quality gate plan, and ask it to return a routing result for the next skill call.

Frequently Asked Questions about change-forge-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route ambiguous product change requests to the correct workflow path?

Change routing handles broad requests by classifying type, risk, and impacted areas to determine the minimum sufficient professional skill path. It outputs a task DAG and quality gates to guide immediate next-step execution.

What is the best way to determine required quality gates for a complex software refactor?

Risk and evidence-aware orchestration evaluates security, data integrity, and production deployment factors to establish required quality gates. It escalates risk for irreversibility and rollback uncertainty, binding only necessary foundation capabilities to the chosen professional skills.

When do I need to attach domain extensions for Web3 or AI changes?

Domain extension gating attaches Web3, AI, mobile, bigdata, payment, or IoT extensions only when clear domain signals exist in the change request. This prevents over-routing by ensuring extensions are applied solely on detected domain-specific evidence.

Does the router handle security and data schema changes without assuming missing evidence?

The router requires evidence-driven classification for security, API, data schema, and reliability changes without assuming missing evidence. It applies risk escalation rules for external integrations and migrations to ensure safe change routing.

Can I use this routing approach for both new features and bug fixes?

Yes, the router applies to requests spanning new features, bug fixes, refactors, release, testing, and documentation. It classifies the change type and selects the smallest professional skill path across intake, impact modeling, and delivery.