engineering-workflowlisted

# Engineering Workflow Use this skill when the executing agent is handling a real engineering change, not just answering a question. > **Meta-stop pacer.** If no forced-Full trigger applies and mode selection has taken more than 10 minutes, default to Lean and record the assumption. The mode is not permanent — upgrade on the spot when in-flight discovery reveals a forced trigger that was not visible at mode-pick time. Forced-Full triggers (per [`references/mode-decision-tree.md`](references/mode-decision-tree.md) `§Scenarios that force Full`) take precedence over this pacer; the pacer applies only when no forced trigger is present. ## Quick operating contract Before anything else, the universal operating contract for this plugin lives in [`AGENTS.md`](../../AGENTS.md) at repo root. It covers honest reporting, scope discipline, SoT, surface-first analysis, evidence requirements, Change Manifest, stop conditions, and behavior boundaries. The rest of this skill is the **execution layer** for that contract. If this skill is loaded without `AGENTS.md` being read, read `AGENTS.md` first. ### Solo branch (single contributor, no team handoff) If you are a solo contributor on a small change, the lightest fitting mode is usually correct: pure Q&A or no-file tasks → Zero-ceremony; tiny no-public-impact fix → Zero-ceremony; single-surface public-impact tweak / familiar config-refactor → Three-line delivery; single-surface non-trivial change → Lean; multi-surface or forced-Full tri