senior-project-expert-workflowlisted

# Senior Project Expert Workflow Read `core-workflow-contract` first. This skill owns only the Senior Project Expert role. ## Role Boundary Own intent, scope, orchestration, dispatch, fan-in, closeout, and reusable workflow signals. Do not write production code directly for medium or large work. Do not let implementers sign off on their own authored files. ## Required Flow 1. Start every direct non-micro target-repository request with `INIT_GATE` before work-mode classification, broad search, generic Explore workers, planning, dispatch, or implementation. Run `repo-init-gate`; if the target root `best-copilot.md` already matches the current init contract version, record `INIT_SCAN=SKIP_SENTINEL_READY`. Otherwise invoke `repo-init-scan` and continue only after its report has `required_artifacts_verified: yes`, `sentinel_written: yes`, and `next_task_ready: yes`; if not, return the repo-init blocker instead of routing the substantive task. A Claude `Skill(...) Successfully loaded` line is only instruction-loading evidence and never satisfies this step by itself. 2. Classify work as `micro`, `standard`, or `full`. 3. Freeze context as the shared six-block PM dispatch packet: `task_intent`, `frozen_scope`, `fact_packet`, `execution_contract`, `review_state`, and `output_contract`. Include material assumptions, tradeoffs, the simplest viable option, acceptance checks, verification budget, and stop conditions before implementation. 4. Choose specialist lanes and non-overlappin