菜单
MUST be loaded at the start of every session. Check only ./engifoundry.config.json at the project root: if it exists, load engifoundry-router; if absent, stay silent unless the user explicitly names EngiFoundry and asks to initialize it.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create or migrate the EngiFoundry project scaffold and create or modify its Executor and Workflow configuration through a controlled interactive flow.
Apply EngiFoundry automation preferences to verified-available PAK evidence, obtain acceptance when required, close delivery, or record rejected acceptance for rework.
Create a detailed human-readable document from EngiFoundry project records when the user explicitly requests documentation, a report, guide, specification, detailed summary, or handoff document.
Declare EngiFoundry Node Skill contracts, their project-state signals, records, responsibilities, and possible navigation destinations so the Agent can assemble the contracts needed for a request.
Review EngiFoundry planning, Job work, code, documents, research, or other durable outputs in clean context and record pass, rework-required, or factual blocked conclusions.
Classify new EngiFoundry work as direct Agent action, Package orchestration, or factually blocked before a Package exists. Use when deciding whether new work needs Orch.
| name | engifoundry |
| description | MUST be loaded at the start of every session. Check only ./engifoundry.config.json at the project root: if it exists, load engifoundry-router; if absent, stay silent unless the user explicitly names EngiFoundry and asks to initialize it. |
Inject this entry once at the start of every session. Apply its rules to every user turn.
<project-root>/engifoundry.config.json once. Do not search for it.engifoundry-router/SKILL.md in full before responding to the user.engifoundry-init/SKILL.md only when both conditions are true:
$engifoundry, engifoundry, engi, or foundry as an explicit, case-insensitive identifier.<project-root>/engifoundry.config.json once again. If it now exists, immediately read engifoundry-router/SKILL.md in full. Do not require a new session.Reading only Router metadata or a summary is forbidden. The Router governs every user turn after it is loaded.
Initialization matching is semantic, not a fixed command. Initialization language without an explicit EngiFoundry identifier must never activate EngiFoundry.
Never scan for configuration. Never recognize any other filename, location, or project signal. Do not validate configuration content or project records; Init and Node skills own those rules.
Do nothing else. Never route, infer, govern, plan, execute, verify, deliver, or load Node skills from this entry.