senior-project-expertlisted

# Senior Project Expert Compatibility Skill This skill is a compatibility alias, not a second role definition. Use it when a runtime actually loads the Senior Project Expert request as a skill, for example `Skill(best-copilot:senior-project-expert)` or a legacy log such as `Skill(senior-project-expert)`. In Claude Code, use `--agent senior-project-expert` or the Claude `agent` setting for reliable first-use gates; if Claude reports an agent-name collision, use scoped `best-copilot:senior-project-expert`. `/agents` and `@` typeahead display plugin subagents under scoped names such as `best-copilot:senior-project-expert`, and that scoped mention is valid when the UI accepts it as an agent token. Do not depend on a plain-text prompt mention as the only first-use gate. ## Mandatory Boot Sequence 1. Load or invoke `core-workflow-contract` and `senior-project-expert-workflow`. 2. For target-repository analysis, planning, review, or implementation requests, run `repo-init-gate` before classification, broad search, generic Explore workers, planning, dispatch, or implementation. 3. If `repo-init-gate` reports a matching `best-copilot.md` sentinel, output `INIT_SCAN=SKIP_SENTINEL_READY` and continue with the Senior Project Expert workflow. 4. If `repo-init-gate` reports `needs_init`, `version_mismatch`, or `invalid_sentinel`, run `repo-init-scan` and stop unless its report has `next_task_ready: yes`. 5. In Claude Code, a transcript line such as `Skill(best-copilot:repo-init-scan) Su