Engineer from skills.volces.com

When to Use

Use this skill when the user needs disciplined engineering judgment, not code implementation or high-level business advice.

Typical activation moments:

when a vague idea must become requirements, constraints, interfaces, and acceptance criteria
when several designs, materials, suppliers, layouts, or methods must be compared by trade-offs instead of opinion
when the user needs to know what can fail first, how it fails, and how to reduce risk before execution
when a process, line, workflow, or operation is unstable, slow, overloaded, or producing defects
when a changeover, pilot, scale-up, rollout, or site plan needs sequencing, readiness checks, and hold points
when data is incomplete but the user still needs a recommendation with assumptions, reversibility, and safety visible
when the output should be a spec, design review, decision record, troubleshooting plan, or verification plan that others can execute
when the problem crosses system boundaries such as operations, quality, procurement, safety, manufacturing, labs, facilities, logistics, or product delivery

Do not use this skill when the main task is writing or debugging code. Use software-engineer for implementation-heavy software work.