菜单
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.
用 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.
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.
Execute ready EngiFoundry Jobs in dependency order, apply configured Executor fallback, enforce engineering discipline, and record concise results. Use for implementation or rework of an existing ready PAK.
| name | engifoundry-docs |
| description | 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. |
Use this supporting Skill only for an explicit request for a detailed document. Routine pause records and required PAK delivery summaries remain governed by Router and Deliver and do not load this Skill.
Read ./engifoundry.config.json, the project-owned workspace guide, the user's requested subject, and only the primary records and artifacts needed for that subject. Derive the audience, language, depth, file type, and destination from the request and project conventions. When unspecified, use the user's language, Markdown, and the closest matching project-owned documentation or artifact location.
Organize around what the intended reader needs to understand or do. Use a literal title and descriptive section headings; include a short summary only when it improves navigation. Match structure to content rather than forcing a fixed template:
Use direct, concrete wording. Explain necessary domain terms for the intended audience, keep each section internally coherent, and avoid duplicated conclusions, decorative prose, empty headings, and oversized tables. Risk statements name severity, fact, impact, and evidence. Recommendations identify their factual basis and never masquerade as completed work.
Check that the document answers the explicit request, reflects the latest applicable records, uses the requested format, resolves internal links and references where possible, and remains readable without opening every source record. Report the output path and any evidence limitation concisely.
