engineer-system-change

Evaluate and execute software system changes using first-principles analysis and rigorous decision gates.

81.2k|11.2k|Updated May 7, 2025

Search Tags:#rfc #System Design #Refactoring #Decision Making #ARCHITECTURE #Software Engineering

One-click install

npx skills add https://github.com/bytedance/deer-flow --skill engineer-system-change

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: engineer-system-change
Source: https://github.com/bytedance/deer-flow/tree/main/.agent/skills/engineer-system-change
Command: npx skills add https://github.com/bytedance/deer-flow --skill engineer-system-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common issue of poorly scoped or speculative software changes that introduce unnecessary complexity, technical debt, or risk to a production system.

Core Features & Use Cases

Decision Gates: Provides a structured framework to validate the necessity of a change, identify semantic consumers, and ensure the solution is proportional to the risk.
Risk Mitigation: Enforces evidence-based assessment before implementation, preventing speculative abstractions and ensuring changes are grounded in verified system behavior.
Use Case: Use this Skill when evaluating a proposed API change or a new system module to determine if the change is truly required, who the consumers are, and if a smaller, less risky alternative exists.

Quick Start

Analyze the proposed system change for the authentication module using the engineer-system-change skill to determine if it meets the required decision gates.

Frequently Asked Questions about engineer-system-change

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

FAQPage Schema

How do I evaluate if a system change is necessary?▼

Use the decision gates to ground the problem in current user workflows and verify if existing capabilities already solve the issue. If no evidence shows a change is needed, the verdict is STOP.

What is a semantic consumer in this context?▼

A semantic consumer is a named caller, component, or user that currently reads or acts on a specific field, API, or module. Changes must be tied to verified current needs of these consumers.

When should I use the REDUCE verdict?▼

Use REDUCE when the problem is real but the proposed scope, abstraction, or implementation plan exceeds the evidence provided. It indicates the solution is oversized for the verified requirement.

How does this skill handle high-risk changes?▼

High-risk changes require proportional verification plans, including production-like rehearsals and executable rollback strategies. The skill mandates evidence-backed claims for all material risks.