Menü
Compatibility entrypoint for runtimes that resolve the Senior Project Expert name as a skill instead of the Senior Project Expert agent. Runs the same init preflight before PM/coordinator workflow.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | senior-project-expert |
| description | Compatibility entrypoint for runtimes that resolve the Senior Project Expert name as a skill instead of the Senior Project Expert agent. Runs the same init preflight before PM/coordinator workflow. |
This is a compatibility alias, not a second role definition. Prefer the real Senior Project Expert agent when the runtime supports agents. If this skill is loaded instead, execute the same lightweight init gate before any target-repository work.
core-workflow-contract and senior-project-expert-workflow.repo-init-gate before classification, broad search, planning, review, dispatch, or implementation.repo-init-gate/scripts/run-preflight.sh <target-root> claude.best-copilot.md, parse only YAML frontmatter, compare the version to the current repo-init-gate contract, and emit ## Repo Init Gate.INIT_SCAN=SKIP_SENTINEL_READY and continue with senior-project-expert-workflow.repo-init-scan on demand. Continue only after required_artifacts_verified: yes, sentinel_written: yes, and next_task_ready: yes.Skill(...) Successfully loaded is not execution evidence. The transcript must show the gate result, and scan output only when the gate fails. Do not load or run repo-init-scan on a current sentinel.
Follow senior-project-expert-workflow: classify, freeze the shared six-block packet, choose named specialist lanes where needed, fan in structured handbacks, verify before completion, and use the native continuation/closeout gate when available.
For non-micro target-repository work, keep the visible trail compact:
INIT_GATE -> [INIT_SCAN if needed] -> CLASSIFY -> FREEZE_PACKET -> LANE_SELECTION -> EXECUTOR_LANES -> FAN_IN -> NEXT_GATE
Use when an agent needs the shared best-copilot contract for source priority, runtime adapters, init gates, work modes, dispatch packets, review, verification, memory, spec, state persistence, or closeout.
Use inside repo-init-scan after the official stage whenever scaffold verification, bounded repair, or `best-copilot.md` rewrite is still needed.
Use when coordinating large, ambiguous, cross-module, multi-agent, planning, dispatch, fan-in, closeout, or workflow-evolution work as the Senior Project Expert.
Use when maintaining requirements, design, tasks, ADRs, execution-plan state, closeout records, or memory/spec recovery as the Specification Writer.
Use when an approved tasks.md from a Spec Bundle, or a compact approved small-work plan, should be executed by fresh-context specialist subagents, with each task receiving implementation, spec-compliance review, code-quality review, and verification before closure. DO NOT USE FOR: missing plans, brainstorming, or simple single-file edits.
Create the target repository's local spec skeleton and reusable requirements/design/tasks templates. Use from repo-init-scan during first substantial plugin use, or from spec-writing flows when `spec/INDEX.md` or `spec/templates` is missing. Do not overwrite active project specs.