ecw

Enterprise Change Workflow (ECW)

中文文档

Give AI the ability to "change one line of code, trace the full-chain impact" in large projects.

---

The Problem

AI assistants excel at independent changes but miss cascading effects in large multi-module systems:

• Changed a Facade method signature — 5 other domains were calling it
• Fixed an MQ message format — 3 external consumers were silently broken
• Accepted a "simple requirement" — it touched a state machine, shared resources, and an end-to-end path

ECW enforces a risk-proportional workflow before any code is written. A log change and an inventory deduction should not require the same process.

---

Risk-Driven Depth

Every change is classified P0–P3. The risk level determines workflow depth — nothing more and nothing less.

Level	Risk	Typical Scenarios
P0	Critical	Multi-domain state machine changes, core path refactoring
P1	High	Shared resource modifications, MQ format changes
P2	Medium	Single-domain field additions, local logic adjustments
P3	Low	Log adjustments, copy changes, config updates

---

How It Works

flowchart TD
    IN_REQ([User: requirement / feature change]) --> RC
    IN_BUG([User: bug report]) --> SD

    RC["🔍 risk-classifier\n(initial risk assessment — quick prediction)"]

    RC -->|Single-domain P0/P1| RE[requirements-elicitation]
    RC -->|Cross-domain 2+| DC["domain-collab\n(parallel agent analysis)"]
    RC -->|P2 / P3| WP

    RE --> WP
    DC --> WP

    SD["systematic-debugging\n(root-cause analysis)"] --> IMPL

    WP["writing-plans"] -->|P0 · P1 cross-domain| SC["spec-challenge\n(adversarial review)"]
    WP -->|P2| IMPL
    SC --> IMPL

    IMPL[Implementation] --> IV
    IV["impl-verify\n(multi-round convergence)"] --> BIA
    BIA["biz-impact-analysis"] --> DONE
    BIA -->|P2/P3| DONE

    DONE([✓ Verified Complete])

    style RC  fill:#EBF8FF,stroke:#63B3ED,color:#2C5282
    style WP  fill:#EBF8FF,stroke:#63B3ED,color:#2C5282
    style IMPL fill:#EBF8FF,stroke:#63B3ED,color:#2C5282
    style IV  fill:#EBF8FF,stroke:#63B3ED,color:#2C5282
    style BIA fill:#EBF8FF,stroke:#63B3ED,color:#2C5282
    style RE  fill:#FEEBC8,stroke:#F6AD55,color:#744210
    style DC  fill:#FEEBC8,stroke:#F6AD55,color:#744210
    style SC  fill:#FED7D7,stroke:#FC8181,color:#742A2A
    style SD  fill:#FED7D7,stroke:#FC8181,color:#742A2A
    style IN_REQ  fill:#C6F6D5,stroke:#68D391,color:#22543D
    style IN_BUG  fill:#FED7D7,stroke:#FC8181,color:#742A2A
    style DONE fill:#C6F6D5,stroke:#68D391,color:#22543D

risk-classifier handles requirement / feature changes only (quick keyword prediction). Bug fixes go directly to ecw:systematic-debugging (see risk-classifier/SKILL.md description).

---

Walkthrough: A Real Scenario

"Add a coupon deduction step to the order submission flow"

1. risk-classifier matches: order submission (P1 floor) + coupon found in shared-resources.md → escalates to P0
2. domain-collab dispatches parallel agents: Order, Coupon, and Payment domains analyze independently
3. Cross-evaluation round: Payment domain flags a double-deduction edge case the others missed
4. writing-plans generates a risk-aware plan with domain context injected from knowledge files
5. spec-challenge runs an independent adversarial review → finds a missing rollback path
6. Implementation proceeds against the corrected plan
7. impl-verify runs 4 parallel rounds: code vs. requirements / domain rules / plan / engineering standards
8. biz-impact-analysis scans git diff → flags downstream impact on loyalty point accrual (an e2e path not mentioned in the requirement)

Without ECW, steps 2–3 and 8 would be invisible.

---

Knowledge-Driven Analysis

ECW's impact analysis depends on project-level knowledge files. Five cross-domain knowledge types form the dependency graph used by risk-classifier, domain-collab, and biz-impact-analysis:

#	File	Content
§1	cross-domain-calls.md	Domain-to-domain call matrix
§2	mq-topology.md	MQ topic publish/subscribe relationships
§3	shared-resources.md	Services/components shared by 2+ domains
§4	external-systems.md	External system integrations
§5	e2e-paths.md	End-to-end critical business paths

Knowledge file quality directly determines analysis accuracy. Java/Spring projects can bootstrap these with the included scanning scripts (see Installation).

---

Multi-Repo Workspace