engineering-workflowlisted

# Engineering Workflow Use this skill for the workflow layer around a repository. Keep product, domain, architecture, operations, QA, security, and release documentation under their existing owners. ## Runtime Invariants - `audit_before_edit: required` - `plan_schema_version: 2` - `instruction_contract_version: 3` - `orchestration_contract_version: 3` - `platform_compatibility_version: 1` - `privacy_review_contract_version: 1` - `repo_change_plan: full_required` - `plan_mode_exit_materialization: required` - `direct_execution_materialization: required` - `shared_state_owner: root` - Audit the target before editing it. - Any task that changes repository state requires a structurally complete active `PLANS.md` plan before implementation, tests, configuration, templates, or other workflow files change. Read-only work is the only exception. - After Plan Mode, materialize the approved plan as the first repository write. Without Plan Mode, derive and materialize the full plan as the first repository write. Preserve outcomes, requirement IDs, sources, decisions, constraints, rejected alternatives, ordered work, validation, recovery, risks, and the exact resume point. - Never replace an active plan with a compressed summary. Run the plan-fidelity check before implementation. - Close or archive a plan through `scripts/plan_lifecycle.py`; a manual `Status: done` edit is not closure. - After compaction, interruption, resume, session change, milestone closure, or handoff, read `PLANS.