engineering-change-analysis

ProfessionalRuntime top level

analysis-agent: implementation-preparation for source-backed changes, diagnosis-only for causes, or source-backed-answer for repo questions; skip source-free, implementation-ready, and accepted-artifact work.

Group: Intake, analysis and planning
Routing mode: evidence-only
Supported roles: MainAnalysisTaskReview
Source: SKILL.md

Use when

Trigger signals that make this skill the right owner

implementation-preparation for source-backed desired-behavior, affected-consumer, and verification analysis before implementation or repair
diagnosis-only for verified cause analysis
source-backed-answer for a repository-dependent engineering question

Do not use when

Anti-triggers — as binding as the triggers above

bounded implementation-ready change whose owner, behavior, and verification are established
source-free question
accepted Engineering Brief already exists and the user explicitly requests one narrow artifact analysis
module-boundary placement decision
dependency-direction placement decision

Required inputs

What must be supplied before this skill can decide anything

explicit mode: implementation-preparation, diagnosis-only, or source-backed-answer
user request or question
bounded repository read scope and known constraints
current source and test evidence discovered within the assigned scope

Output contract

What this skill owes the next role

implementation-preparation result defined by references/implementation-preparation.md with one initial Analysis or protected-decision Delta Analysis
diagnosis-only result defined by references/diagnosis-only.md
source-backed-answer result defined by references/source-backed-answer.md
source-backed affected-consumer evidence and unresolved structural-risk handoff to architecture-impact-reviewer

Escalation signals

When this skill must hand the decision back

scope, authority, or material risk exceeds the selected task contract

Related expertise

37 Layer 3 candidates may be loaded behind this skill. A single task loads at most three, and only when the current evidence justifies them.

Targeted references

Each reference carries its own load condition. None of them enter context by default.

Reference	Load when	Do not load when	Required by
checklist.mddecision-checklist	A bounded review needs a concrete surface inventory across product, UX, domain, API, data, frontend, backend, integrations, security, tests, release, observability, and docs	Evidence freshness, consumer proof, or performance blast radius is the core risk	Analysis
diagnosis-only.mdmode-contract	engineering change analysis selects diagnosis-only	engineering change analysis is executing another mode	Analysis
evidence-patterns.mdevidence-pattern	Closure depends on changed-surface-to-validation mapping, same-pattern scan proof, consumer evidence, rollback limits, graph/report freshness, or proof limits	Only high-level routing is needed and evidence is not being closed	Analysis
implementation-preparation.mdmode-contract	engineering change analysis selects implementation-preparation	engineering change analysis is executing another mode	Analysis
index.mdindex	competing engineering change analysis references require dependency, conflict, or output-fragment selection	the engineering change analysis root or a task-named reference already resolves selection	Analysis
solution-optimality.mdtargeted	Performance/resource blast radius may include CPU, memory, network, disk, lock contention, throughput, or latency	No performance-sensitive path or resource tradeoff is material	Analysis
source-backed-answer.mdmode-contract	engineering change analysis selects source-backed-answer	engineering change analysis is executing another mode	Analysis