Engineering

Overview

Build the smallest production-complete change that delivers the requested outcome. This skill owns inspection, implementation, proof, and the completion claim. Keep that loop together; separate planning, testing, or verification producer skills do not share its ownership.

When to Use

• Features, understood bug fixes, refactors, migrations, and implementation plans
• Read-only research or design for a known software objective
• Greenfield work whose next useful behavior can be sliced vertically

When Not to Use

• Use debugging when the cause or failing boundary is unknown
• Use test-design when tests, TDD, coverage, or proof design are the primary deliverable
• Use the matching review, audit, branch, or handoff skill when that is the actual task
• Add writing-rust, effect-ts, or designing-data-intensive-systems only as a modifier when its domain pressure is present