engineering

The change stays focused on the behavior you requested. The agent avoids speculative options, dependencies, abstractions, and nearby cleanup while preserving validation, error handling, security, and meaningful tests.

Install the Workflow plugin, then ask for the code change in plain words. The agent selects engineering when the request matches; you do not need a special command. For example:

Fix the off-by-one error in the date picker's week numbers.

Use it for a feature, bug fix, refactor, failing test, CI failure, or review feedback you want checked or applied. An explanation alone does not need it. For a direction, specification, plan, or tickets without code edits, use planning.

The agent reads the code that owns the behavior and the nearest tests. It runs a suitable existing test before editing. For larger work, it states a plan and compares it with a simpler option. If no change is needed, it stops.

Correct tests constrain the fix. The agent changes a test only when evidence shows it is wrong or its contract changed on purpose. New coverage must catch a regression existing tests miss; a bug regression test must fail on the old code first.

Work that spans several tasks or PRs runs as a loop for each task: plan, implement, verify, review, and fix, until the task's completion signal holds. Each PR is a review boundary: before it reaches you, an agent that did not write it reviews the whole PR. A PR that is one routine, bounded change needs only focused checks. A final review you asked for, such as a sol-loop or full-send, runs on each finished PR, not on each task.

After editing, the agent reruns the affected checks and inspects the diff for accidental changes, duplication, and dead code. Substantial coverage changes get a test-audit. Risky work, such as migrations or security changes, needs review by an agent that did not write it, when the host supports that review.

Workers and reviewers keep further delegation within the brief's authority. Truncated output sends the agent to the named artifact first. Credential and token diagnostics reveal only whether a value is present.

SKILL.md has the exact implementation and verification contract.

• The requested change, with the commands run and their results.
• Remaining risks and checks that could not run, reported as unverified.

Engineering does not commit, push, or publish without your authorization.