R — Original text (Reading)
The Yellow Emperor asked: Diseases have branch and root, and needling has contrary and supportive approaches. How is this so? Qi Bo replied: In general, the methods of needling must distinguish yin and yang, with front and back corresponding to each other, contrary and supportive applied appropriately, and branch and root shifting into each other. Therefore it is said: there are cases where the branch is affected and one seeks treatment at the branch; there are cases where the root is affected and one seeks treatment at the root; there are cases where the root is affected and one seeks treatment at the branch; there are cases where the branch is affected and one seeks treatment at the root. Thus in treatment there are those who obtain results by treating the branch, and those who obtain results by treating the root. One who knows branch and root will succeed in ten thousand attempts; one who does not know branch and root is said to act recklessly. If disease comes first and then counterflow arises, treat its root; if counterflow comes first and then disease arises, treat its root; if cold comes first and then disease arises, treat its root; if heat comes first and then abdominal fullness arises, treat its branch. People have guest qi and identical qi. If urination and defecation are not free, treat its branch; if urination and defecation are free, treat its root. When disease outbreaks with excess, treat the root and then the branch: first treat its root, then treat its branch; when disease outbreaks with deficiency, treat the branch and then the root: first treat its branch, then treat its root. When it is mild, carry them out together; when it is severe, carry it out alone.
— The Yellow Emperor/Qi Bo, Basic Questions, Chapter 65: Discussion of Branch and Root and Disease Transmission
I — Methodological skeleton (Interpretation)
The branch-and-root urgency decision framework is used to determine handling priorities among multiple intertwined problems.
Its core concepts and operating rules:
-
Definition of branch and root: "Root" is the problem that occurs first, the fundamental cause; "branch" is the problem that occurs later, the surface symptom. The earlier disease is the root, the later disease is the branch. The root determines the direction of the branch, and the branch reflects the state of the root.
-
Branch and root are not fixed: "Branch and root shift into each other"—under specific conditions, the roles of branch and root can be exchanged. When the branch (surface problem) has become severe enough to endanger the system, it becomes an "acute condition" that must be dealt with first, and its priority instead becomes higher than that of the root.
-
Three priority rules:
- General rule: Treat the root first (first resolve the fundamental cause, and the symptoms will subside accordingly).
- Acute-condition exception: For acute conditions such as abdominal fullness (digestive blockage) and inhibited urination and defecation (blocked excretion), even if they are the branch, they must still be treated first.
- Deficiency-excess rule: For excess (excess pattern), treat the root first and then the branch; for deficiency (deficiency pattern), treat the branch first to stabilize the situation, then treat the root.
-
Mild-severe principle: "When it is mild, carry them out together; when it is severe, carry it out alone"—when the problem is not very severe, branch and root can be treated simultaneously; when the problem is very severe, forces must be concentrated to deal with them one by one.
The essence of this framework lies in this: it is not simply "treat the root first," but rather a conditional, dynamically adjustable priority system.
A1 — Application in the book (Past Application)
Case 1: Heat first and then abdominal fullness—transformation of branch and root
- Problem: A person first has fever (root), and later develops abdominal distention and fullness (branch). According to the general rule, the root should be treated first (reduce the fever), but here Qi Bo says, "If heat comes first and then abdominal fullness arises, treat its branch."
- Use of the methodology: Although fever is the root, the abdominal fullness (blockage of the digestive system) has already become an acute condition—digestion is blocked, the power of medicine cannot be absorbed, and the body's nutrition is cut off. At this time, the conditions for treating the root (reducing the fever) are not present.
- Conclusion: Although the branch (abdominal fullness) arose later, it has already become the key bottleneck obstructing everything. Only by first clearing the abdominal fullness are conditions present to reduce the fever.
- Result: First use the draining method to relieve the middle fullness, then use the clearing-heat method to treat the root. This reflects "the branch and root shift mutually"—an acute condition can elevate the branch to a priority item.
Case 2: The disease arises with deficiency—treat the branch first, then the root
- Question: When a disease manifests as "deficiency" (deficiency pattern/functional decline), which should be treated first, the root or the branch?
- Use of the methodology: "When the disease arises with deficiency, treat the branch as the root: first treat the branch, then treat the root." A deficiency pattern means the system is already very weak; directly attacking the root (eliminating the root cause) will further consume the system.
- Conclusion: In a deficiency pattern, one must first support the healthy qi (treat the branch, stabilize the current state), and only after the system has some capacity to bear it should one treat the root.
- Result: This rule prevents the erroneous decision of "fierce attack on a deficient person" that leads to system collapse.
A2 — Trigger scenarios (Future Trigger) ★
In what situations will users need this skill?
- Multiple interwoven problems: The user faces more than 3 problems at the same time, and these problems have causal relationships—some are causes (root), some are effects (branch)—and they do not know which to tackle first.
- The dispute over treating the branch versus the root: The user or team is arguing over "solve the surface problem first" versus "solve the root cause first," and needs a clear decision-making framework to break the deadlock.
- Limited resources require prioritization: Resources (time, energy, budget) are only enough to handle part of the problems; priorities must be determined, and the priorities need dynamic adjustment (because treating A may affect B).
Linguistic signals (activate when these appear in the user's speech)
- "There are too many problems; I don't know which to solve first"
- "Treating the symptoms, not the root cause" or "must solve it at the root"
- "The surface problem is X, but I think the root is Y"
- "Putting out fires while fires keep starting; it just won't stop"
- "Handle the urgent first or handle the important first"
Distinction from adjacent skills
- Difference from
yin-yang-balance: what yin-yang balance solves is "direction" (whether to tonify or drain), while branch-root priority and urgency solves "sequence" (which to do first and which later). - Difference from
five-elements-network: what the five phases generating and overcoming reveals is "transmission path" (how the problem spreads), while branch-root priority and urgency reveals "processing sequence" (where on the transmission path to begin intervention).
E — Executable steps (Execution)
After the skill is activated, the agent should execute the following steps:
-
List all problems: complete inventory
- List all problems the user currently faces, without omission. For each problem, note: time of occurrence (sequence), severity, and whether it affects the system's basic operation.
- Completion standard: the problem inventory is complete, and every problem has a timeline and severity annotation.
-
Determine branch and root + determine priority and urgency: two-dimensional classification
- Determine branch and root: Based on causal relationships and temporal sequence, mark each problem as "root" (earlier onset/root cause) or "branch" (later onset/result).Determine priority and urgency: Check whether there is an "acute condition"—that is, a problem that has already endangered the system's basic operation (analogous to "middle fullness" or "inability to urinate or defecate"), regardless of whether it is branch or root.
- Completion criteria: Each problem has two labels—[root/branch] and [urgent/non-urgent]. At least one "root" and one urgent condition are identified (if any).
- Stopping condition: If there is only one problem, no root-branch analysis is needed; directly provide the solution to that problem.
-
Determine treatment order: formulate a priority plan
- Apply three rules: (1) if there is an urgent condition, treat the urgent first (regardless of root or branch); (2) when there is no urgent condition, treat the root first; (3) when the system is weak, support the healthy qi first (branch first, then root). Mark opportunities for "when both are present, treat them in parallel"—which problems can be handled simultaneously.
- Completion criteria: Provide an ordered action list (what to do first, what to do second), and explain why each step has that priority.
B — Boundary ★
Do not use this skill in the following situations
- A single clear problem: If there is only one problem to solve, there is no distinction of "root/branch," and this framework has no role.
- Urgent crisis: When the system is collapsing (such as massive bleeding or a system outage), there is no time to analyze root-branch and urgency; you must first do whatever can stabilize the situation. Root-branch analysis is a decision-making tool for after there is basic breathing room.
Failure modes the author warns about in the book
- Not knowing root and branch is called reckless action: Acting without distinguishing root and branch is equivalent to blind action—you may spend a large amount of resources treating the branch while the root remains untouched; or you may force treatment of the root but the system is too weak to bear it.
- Ignoring the shifting of root and branch: The roles of root and branch are not fixed. An urgent condition can elevate the "branch" to first priority. If you cling to the dogma of "treat the root first," you will miss the timing when there is an urgent condition.
The author's blind spots / limitations of the era
- The root-branch framework in the Suwen uses disease as its default scenario, and the specific definitions of "urgent condition" (abdominal fullness, difficulty in urination and defecation) are medical. When applying it in other domains, what counts as an "urgent condition" needs to be redefined—usually a problem where "if not handled immediately, the system will collapse in the short term."
- The framework assumes that the causal relationships among problems are clear, but in reality the causal chains of multiple problems may be entangled, making it difficult to determine which is root and which is branch. In this case, other analytical frameworks (such as yin-yang-balance) need to be combined to first clarify the relationships.
Adjacent methodologies easily confused with it
- Eisenhower Matrix (urgent/important): Similar in form (two-dimensional classification), but root-branch and urgency/non-urgency add a "causal relationship" dimension—root and branch are not two independent attributes, but a sequential relationship with a causal chain.
- Root Cause Analysis (RCA): Focuses on finding the root cause, but does not provide conditional rules for "when surface problems should be handled first."
Related skills (to be filled in phase 3)
- contrasts-with: prevention-strategy — root-branch and urgency/non-urgency is priority decision-making "after illness has occurred" (multiple problems have already occurred; which to treat first), while treating before illness is a preventive strategy "when illness has not yet occurred" (problems have not yet occurred; how to prevent them). The former is post hoc ordering, the latter is ex ante prevention; the two perspectives are complementary, but the timing of intervention is completely different.
Audit information
- Verification passed: V1 ✓ / V2 ✓ / V3 ✓
- Test pass rate: {{%}} (see test-prompts.json)
- Distillation time: {{DATE}}